Triple
T33648298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Island of Sodor |
E862021
|
entity |
| Predicate | railwayController |
P44064
|
FINISHED |
| Object | Sir Topham Hatt |
—
|
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: Sir Topham Hatt | Statement: [Island of Sodor, railwayController, Sir Topham Hatt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayController Context triple: [Island of Sodor, railwayController, Sir Topham Hatt]
-
A.
railwayControlledBy
chosen
Indicates that the operation, management, or authority over a railway is exercised by a specified controlling entity.
-
B.
railwayInfrastructureManager
Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
-
C.
railRegulator
Indicates that an entity serves as an authority responsible for overseeing, regulating, or enforcing rules within the railway or rail transport sector.
-
D.
railInterface
Indicates a connection or interaction between entities via a rail-based system or interface.
-
E.
railComponent
Indicates a relationship where one entity is a structural or functional part of a rail or railway system component of another entity.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:42 a.m.