Triple
T31510156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby Castle, Douglas |
E803919
|
entity |
| Predicate | isSouthernEndOf |
P5249
|
FINISHED |
| Object | Manx Electric Railway main line |
E229677
|
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: Manx Electric Railway main line | Statement: [Derby Castle, Douglas, isSouthernEndOf, Manx Electric Railway main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSouthernEndOf Context triple: [Derby Castle, Douglas, isSouthernEndOf, Manx Electric Railway main line]
-
A.
hasSouthernTerminus
chosen
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
B.
isEasternEndOf
Indicates that one entity forms or marks the easternmost end or boundary of another entity.
-
C.
isOnSouthernPartOf
Indicates that one entity is located on the southern part or southern region of another entity.
-
D.
isSouthernObject
Indicates that one object is located to the south of, or in the southern part relative to, another reference point or region.
-
E.
southernTerminusVariant
Indicates a variant or alternative form of the southern endpoint or terminus of something (such as a route, line, or boundary).
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a21b77dc8190aa111fcd57ed42ee |
completed | May 3, 2026, 1:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b562a528c819089774c34089107a0 |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:49 p.m.