Triple
T30071169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A1 Steam Locomotive Trust |
E764185
|
entity |
| Predicate | usesDesignsFrom |
P40514
|
FINISHED |
| Object | London and North Eastern 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: London and North Eastern Railway | Statement: [A1 Steam Locomotive Trust, usesDesignsFrom, London and North Eastern Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDesignsFrom Context triple: [A1 Steam Locomotive Trust, usesDesignsFrom, London and North Eastern Railway]
-
A.
designsFor
chosen
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
B.
designsBy
Indicates that one entity is the creator or designer responsible for the conception or design of another entity.
-
C.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
D.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
E.
usesDesignModel
Indicates that one entity applies or relies on a particular design model in performing its function or defining its structure.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 7 p.m.