Triple
T8349088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORP |
E196113
|
entity |
| Predicate | hasRailcodeType |
P56964
|
FINISHED |
| Object | three-letter alpha code |
—
|
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: three-letter alpha code | Statement: [ORP, hasRailcodeType, three-letter alpha code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailcodeType Context triple: [ORP, hasRailcodeType, three-letter alpha code]
-
A.
railroadCodeFor
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
B.
hasRailwayInfrastructureType
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
C.
hasRailConfiguration
Indicates that an entity is associated with, or characterized by, a particular arrangement or setup of rails.
-
D.
hasTypeCode
chosen
Indicates that an entity is associated with a specific type classification represented by a code.
-
E.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8016c4188190a5ff93078e74dc39 |
completed | March 31, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:58 p.m.