Triple
T33811973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toby the Tram Engine |
E866559
|
entity |
| Predicate | fictionalRailway |
P125068
|
FINISHED |
| Object | North Western Railway |
—
|
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: North Western Railway | Statement: [Toby the Tram Engine, fictionalRailway, North Western Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalRailway Context triple: [Toby the Tram Engine, fictionalRailway, North Western Railway]
-
A.
inspiredFictionalRailway
Indicates that a real-world railway served as the creative basis or model for a fictional railway.
-
B.
originalRailway
Indicates that a railway is the first or initial line from which others in a network, route, or system originate or are derived.
-
C.
hasFictionalTransportLink
chosen
Indicates that there is a transportation connection between entities that exists only in a fictional or imagined context.
-
D.
inspiredByRealRailway
Indicates that something is based on, modeled after, or influenced by an actual real-world railway system or line.
-
E.
formerRailroad
Indicates that an entity was previously a railroad but no longer functions as one.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 1:46 a.m.