Triple
T24443222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoreliner IV |
E616324
|
entity |
| Predicate | railwayCoachType |
P47469
|
FINISHED |
| Object | locomotive‑hauled coach |
—
|
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: locomotive‑hauled coach | Statement: [Shoreliner IV, railwayCoachType, locomotive‑hauled coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayCoachType Context triple: [Shoreliner IV, railwayCoachType, locomotive‑hauled coach]
-
A.
railwayCarriageUsedFor
Indicates that a railway carriage is employed or designated for a particular purpose, function, or type of use.
-
B.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
C.
railwayClass
Indicates the specific classification or category assigned to a railway or railway service within a defined system.
-
D.
railroadClass
Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
-
E.
carriageType
chosen
Indicates the specific kind or category of carriage associated with or used in relation to an 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29851e6cc8190a8f160cbed4e9ab0 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.