Triple
T11008024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna |
E260170
|
entity |
| Predicate | waitedFor |
P60668
|
FINISHED |
| Object | redemption of Jerusalem |
—
|
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: redemption of Jerusalem | Statement: [Anna, waitedFor, redemption of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waitedFor Context triple: [Anna, waitedFor, redemption of Jerusalem]
-
A.
awaited
chosen
Indicates that one entity is expected or looked forward to by another, typically involving a period of waiting for its arrival, occurrence, or response.
-
B.
delayedUntil
Indicates that the occurrence or effect of one event or condition is postponed and does not take place until a specified later event, time, or condition is reached.
-
C.
attendsTo
Indicates that one entity directs care, attention, or service toward another entity or task.
-
D.
eventuallyOverrunBy
Indicates that one entity is ultimately defeated, overwhelmed, or taken over by another entity or force after some passage of time.
-
E.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79757bdcc8190900b267826eece21 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.