Triple
T8255216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Spike ceremony |
E193053
|
entity |
| Predicate | railConnectionType |
P54048
|
FINISHED |
| Object | coast-to-coast rail connection |
—
|
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: coast-to-coast rail connection | Statement: [Golden Spike ceremony, railConnectionType, coast-to-coast rail connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railConnectionType Context triple: [Golden Spike ceremony, railConnectionType, coast-to-coast rail connection]
-
A.
countryRailConnection
Indicates that there is a railway connection or service linking two countries.
-
B.
railInterface
chosen
Indicates a connection or interaction between entities via a rail-based system or interface.
-
C.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
D.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
-
E.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78f9f680819088f1d56e0f98974f |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.