Triple
T30733634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Promontory Peninsula |
E782485
|
entity |
| Predicate | railroadEventNearby |
P170080
|
FINISHED |
| Object | driving of the Golden Spike |
—
|
NE NERFINISHED |
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: driving of the Golden Spike | Statement: [Promontory Peninsula, railroadEventNearby, driving of the Golden Spike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadEventNearby Context triple: [Promontory Peninsula, railroadEventNearby, driving of the Golden Spike]
-
A.
hasNearbyRailway
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
B.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
-
C.
nearCommuterRailStation
Indicates that one entity is located close to, or within a short walking distance of, a commuter rail station.
-
D.
nearestRailwayLine
Indicates that one railway line is the closest in distance to a given location or feature compared to all other railway lines.
-
E.
railPortalLocation
Indicates the geographic location or position of a rail portal (such as a tunnel or access point) relative to other referenced entities.
- F. None of above. chosen
Provenance (4 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68ee54d1c8190a4c020394f7fb19a |
completed | May 2, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:37 p.m.