Triple
T10255021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elfstone |
E240438
|
entity |
| Predicate | borneBy |
P2834
|
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: [Elfstone, borneBy, Aragorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aragorn Context triple: [Elfstone, borneBy, 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.
Isildur
Isildur is a legendary Númenórean prince and later King of Gondor and Arnor in J.R.R. Tolkien’s legendarium, best known for cutting the One Ring from Sauron’s hand and ultimately failing to destroy it.
-
C.
É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.
-
D.
Elessar
Elessar is the royal name of Aragorn, the Dúnedain ranger who becomes King of Gondor in J.R.R. Tolkien’s The Lord of the Rings.
-
E.
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.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d24c69ac81908b4da53d13407ac8 |
completed | April 7, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4415b7f848190a9fc8b08824f0b9b |
completed | April 19, 2026, 2:43 a.m. |
Created at: April 6, 2026, 11:30 a.m.