Triple
T37368923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ered Nimrais |
E927783
|
entity |
| Predicate | runsWestToEastAcross |
P28901
|
FINISHED |
| Object | Gondor |
—
|
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: Gondor | Statement: [Ered Nimrais, runsWestToEastAcross, Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsWestToEastAcross Context triple: [Ered Nimrais, runsWestToEastAcross, Gondor]
-
A.
runsWestFrom
Indicates that one entity extends or moves in a westward direction starting from another entity.
-
B.
runsAcross
chosen
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
C.
eastStartingForward
Indicates that an entity begins moving or facing in a forward direction oriented toward the east.
-
D.
ruleWhenCrossingEastward
Indicates the rule or condition that applies when an entity crosses or moves in an eastward direction.
-
E.
westStartingForward
Indicates that an entity serves as the starting forward player for a team or lineup associated with the west (e.g., a western conference, division, or region).
- 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.