Triple
T32096932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Bridge of Khazad-dûm |
E819743
|
entity |
| Predicate | locationInWorld |
P76038
|
FINISHED |
| Object | Middle-earth |
E46050
|
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: Middle-earth | Statement: [Battle of the Bridge of Khazad-dûm, locationInWorld, Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInWorld Context triple: [Battle of the Bridge of Khazad-dûm, locationInWorld, Middle-earth]
-
A.
positionInWorlds
Indicates that an entity occupies specific spatial coordinates or locations within one or more distinct worlds or environments.
-
B.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
C.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
D.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
-
E.
positionOnEnvironment
Indicates the spatial placement or location of an entity relative to a surrounding environment or surface.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a021706e21c81909b83e2b4d9c4130c |
completed | May 11, 2026, 5:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eddf768448190b98751e5c40e0bce |
completed | June 14, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_6a0216861214819097d2177755bc19d7 |
completed | May 11, 2026, 5:48 p.m. |
Created at: May 1, 2026, 12:26 a.m.