Triple
T746042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London, Midland and Scottish Railway |
E15342
|
entity |
| Predicate | fleetIncluded |
P10916
|
FINISHED |
| Object | steam locomotives |
—
|
LITERAL 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: steam locomotives | Statement: [London, Midland and Scottish Railway, fleetIncluded, steam locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetIncluded Context triple: [London, Midland and Scottish Railway, fleetIncluded, steam locomotives]
-
A.
fleetIncludes
chosen
Indicates that a particular fleet contains or is composed of the specified entity or entities as its members.
-
B.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
C.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
D.
fleetSize
Indicates the total number of vehicles, vessels, or units that collectively make up a fleet associated with an entity.
-
E.
fleetFlagshipOf
Indicates that one entity serves as the primary or leading flagship of a particular fleet.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62ca1d081908e3191411f86498d |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.