Triple
T36545482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Marshes |
E901128
|
entity |
| Predicate | travelRouteOnQuest |
P183780
|
FINISHED |
| Object | journey to Mordor |
—
|
LITERAL 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: journey to Mordor | Statement: [Dead Marshes, travelRouteOnQuest, journey to Mordor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelRouteOnQuest Context triple: [Dead Marshes, travelRouteOnQuest, journey to Mordor]
-
A.
travelRouteInStory
Indicates the path or route taken by a character or entity during a journey as described within a narrative or story.
-
B.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
C.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
D.
questlineFeature
chosen
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
E.
travelRouteRole
Indicates the specific functional role an entity plays within a travel route, such as origin, destination, or intermediate stop.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:11 p.m.