Triple
T8400509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guiney Station |
E198156
|
entity |
| Predicate | railroadEra |
P28401
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Guiney Station, railroadEra, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadEra Context triple: [Guiney Station, railroadEra, 19th century]
-
A.
rollingStockEra
Indicates the historical or operational time period during which a particular piece of rolling stock is designed to represent or is considered appropriate.
-
B.
hasRailroadHistory
chosen
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
C.
historicalTramEra
Indicates that the subject is associated with a specific historical period or era in which tram systems operated or were characteristic.
-
D.
formerRailroad
Indicates that an entity was previously a railroad but no longer functions as one.
-
E.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb824bfcbc8190b26bfcb5f8c4777c |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.