Triple
T2182001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gimli |
E49064
|
entity |
| Predicate | friend |
P8712
|
FINISHED |
| Object | Aragorn |
E47099
|
NE 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: Aragorn | Statement: [Gimli, friend, Aragorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aragorn Context triple: [Gimli, friend, Aragorn]
-
A.
Aragorn
chosen
Aragorn is a central heroic figure in J.R.R. Tolkien's Middle-earth legendarium, a ranger and rightful king who plays a crucial role in the defeat of Sauron.
-
B.
Éomer
Éomer is a valiant warrior of Rohan who becomes its king and plays a crucial role in the War of the Ring in J.R.R. Tolkien’s Middle-earth legendarium.
-
C.
Legolas
Legolas is an Elven prince and master archer from Mirkwood who is a key member of the Fellowship of the Ring in J.R.R. Tolkien’s Middle-earth legendarium.
-
D.
Boromir
Boromir is a valiant yet conflicted warrior of Gondor and member of the Fellowship of the Ring in J.R.R. Tolkien’s The Lord of the Rings.
-
E.
Théoden
Théoden is the aging but valiant King of Rohan in J.R.R. Tolkien’s Middle-earth legendarium, who overcomes manipulation to lead his people in the war against Sauron.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbef1f8c0819084da6002035bbf93 |
completed | March 7, 2026, 6 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae95f7e5448190a31dcb5ba3c547fb |
completed | March 9, 2026, 9:42 a.m. |
Created at: March 4, 2026, 7:45 p.m.