Triple
T37378388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paths of the Dead |
E928358
|
entity |
| Predicate | exitsAt |
P188006
|
FINISHED |
| Object | Morthond Vale |
—
|
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: Morthond Vale | Statement: [Paths of the Dead, exitsAt, Morthond Vale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exitsAt Context triple: [Paths of the Dead, exitsAt, Morthond Vale]
-
A.
exitedAt
Indicates that an entity left or departed from a specific location, state, or context at a particular point in time.
-
B.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
C.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
D.
hasExits
Indicates that an entity provides one or more ways out or routes leading from it to other locations or states.
-
E.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
- F. None of above. chosen
Provenance (4 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.