Triple
T38644764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War of the Thorns |
E938686
|
entity |
| Predicate | locationInvolved |
P76462
|
FINISHED |
| Object | Teldrassil |
E2228608
|
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: Teldrassil | Statement: [War of the Thorns, locationInvolved, Teldrassil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInvolved Context triple: [War of the Thorns, locationInvolved, Teldrassil]
-
A.
involvedLocation
chosen
Indicates that an event, action, or relationship takes place in, or is significantly associated with, a particular location.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
D.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
-
E.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
- F. None of above.
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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42341c2f6c8190b30eb967b8de17d3 |
completed | June 29, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.