Triple
T36293411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Region |
E893293
|
entity |
| Predicate | hadMajorTerminus |
P388
|
FINISHED |
| Object | London King’s Cross |
—
|
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: London King’s Cross | Statement: [Eastern Region, hadMajorTerminus, London King’s Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMajorTerminus Context triple: [Eastern Region, hadMajorTerminus, London King’s Cross]
-
A.
hadMajorFront
Indicates that an entity (such as a conflict or war) involved a significant primary front or theater of operations in a specified location or context.
-
B.
terminus
chosen
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
otherMajorTragedy
Indicates that the subject experienced or was involved in a significant tragic event other than the primary or most notable tragedy under consideration.
-
D.
isMajorDamOf
Indicates that one dam is the primary or most significant dam associated with a particular river, reservoir, or water system.
-
E.
lastMajorCollapse
Indicates the most recent significant breakdown or failure event that occurred in relation to the subject.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.