Triple
T9811995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Éomer |
E238294
|
entity |
| Predicate | allegiance |
P1201
|
FINISHED |
| Object | Rohan |
E261161
|
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: Rohan | Statement: [Éomer, allegiance, Rohan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rohan Context triple: [Éomer, allegiance, Rohan]
-
A.
Rohan
chosen
Rohan is a prominent kingdom of horse-lords in J.R.R. Tolkien’s Middle-earth, renowned for its vast grasslands and skilled cavalry.
-
B.
Rohan
Rohan is a masculine given name of Sanskrit origin commonly used in India and among the Indian diaspora.
-
C.
Ravi
Ravi is a common Indian male given name of Sanskrit origin meaning "sun" or "sun god."
-
D.
Ravi
Ravi is one of the major rivers of northern India and Pakistan, flowing through the Punjab region and serving as an important tributary of the Indus River system.
-
E.
Raj
Raj is the given name of Raj Reddy, a pioneering computer scientist known for his foundational work in artificial intelligence and robotics.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb222ba788190a9085272a3de7852 |
completed | April 2, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e41725948190a40ddcf9552e9bf1 |
completed | April 5, 2026, 4:24 a.m. |
Created at: March 30, 2026, 8:30 p.m.