Triple
T37369157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oath of the Men of the Mountains to Isildur |
E927789
|
entity |
| Predicate | fulfilledForHeir |
P108444
|
FINISHED |
| Object | Aragorn |
—
|
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: Aragorn | Statement: [Oath of the Men of the Mountains to Isildur, fulfilledForHeir, Aragorn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fulfilledForHeir Context triple: [Oath of the Men of the Mountains to Isildur, fulfilledForHeir, Aragorn]
-
A.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
-
B.
succeededAsHeir
Indicates that one entity became the heir in place of, or following, another entity, typically upon the latter’s death or abdication.
-
C.
usedByHeir
Indicates that something is utilized or employed by an heir.
-
D.
isHeirExpectedBy
Indicates that one entity is anticipated or designated to inherit from, succeed, or receive rights from another entity.
-
E.
fulfilledVow
chosen
Indicates that an entity has carried out or honored a previously made vow or promise.
- 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_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.