Triple
T37369156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oath of the Men of the Mountains to Isildur |
E927789
|
entity |
| Predicate | fulfilledDuring |
P43883
|
FINISHED |
| Object | War of the Ring |
—
|
NE NERFINISHED |
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: War of the Ring | Statement: [Oath of the Men of the Mountains to Isildur, fulfilledDuring, War of the Ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fulfilledDuring Context triple: [Oath of the Men of the Mountains to Isildur, fulfilledDuring, War of the Ring]
-
A.
concludedDuring
Indicates that an event, process, or state ended within the temporal bounds of another specified time period or event.
-
B.
executedDuring
chosen
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
C.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
D.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
E.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.