Triple
T38453318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glennock |
E912234
|
entity |
| Predicate | railwaySystemInUniverse |
P522
|
FINISHED |
| Object | Sodor railway network |
—
|
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: Sodor railway network | Statement: [Glennock, railwaySystemInUniverse, Sodor railway network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwaySystemInUniverse Context triple: [Glennock, railwaySystemInUniverse, Sodor railway network]
-
A.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
B.
railwaySystemPartOf
Indicates that one railway-related component or subsystem belongs to, is included within, or forms a constituent part of a larger railway system.
-
C.
hasRailSystem
chosen
Indicates that an entity possesses or is served by a rail-based transportation system.
-
D.
railwayFocus
Indicates that something is a primary subject, theme, or point of attention specifically in the context of railways or railway-related matters.
-
E.
railwaySystemServed
Indicates that a railway system provides service to, or operates within, a specified location or area.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:31 p.m.