Triple
T7007839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannah |
E162501
|
entity |
| Predicate | resists |
P55657
|
FINISHED |
| Object | anti-Jewish persecution in Tomainia |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: anti-Jewish persecution in Tomainia | Statement: [Hannah, resists, anti-Jewish persecution in Tomainia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resists Context triple: [Hannah, resists, anti-Jewish persecution in Tomainia]
-
A.
resistedIn
chosen
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
B.
isResistant
Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
-
C.
typeOfResistance
Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
-
D.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
E.
methodOfResistance
Indicates a way or technique by which resistance is carried out or expressed.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc36e3fc8190957445132a9ffb5f |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.