Triple
T12479259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S8 Stock |
E298260
|
entity |
| Predicate | carriageConfiguration |
P26476
|
FINISHED |
| Object | 8-car train |
—
|
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: 8-car train | Statement: [S8 Stock, carriageConfiguration, 8-car train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriageConfiguration Context triple: [S8 Stock, carriageConfiguration, 8-car train]
-
A.
carriageType
Indicates the specific kind or category of carriage associated with or used in relation to an entity.
-
B.
trainConfiguration
chosen
Indicates the specific arrangement and composition of train elements (such as locomotives and cars) used together for a particular operation or service.
-
C.
railCarries
Indicates that a rail or railway system transports or conveys a specified entity from one place to another.
-
D.
locomotiveConfiguration
Indicates the specific arrangement and type of power and running units (e.g., wheel or axle layout) that define how a locomotive is configured.
-
E.
railwayCarriageUsedFor
Indicates that a railway carriage is employed or designated for a particular purpose, function, or type of use.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.