Triple
T187974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMTK |
E4024
|
entity |
| Predicate | railroadType |
P522
|
FINISHED |
| Object | passenger railroad |
—
|
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: passenger railroad | Statement: [AMTK, railroadType, passenger railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadType Context triple: [AMTK, railroadType, passenger railroad]
-
A.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
B.
railroadEngineeringFeature
Indicates a feature, element, or characteristic specifically related to the design, construction, or operation of railroad engineering systems.
-
C.
hasRailSystem
chosen
Indicates that an entity possesses or is served by a rail-based transportation system.
-
D.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
E.
trains
Indicates that one entity teaches, instructs, or coaches another entity to develop skills, knowledge, or abilities.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594940e48190a3d8efbce46241c3 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25672332081909386f35f3ca15dd2 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.