Triple
T29544181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pike’s Peak Gold Rush |
E749584
|
entity |
| Predicate | transportRouteUsed |
P94946
|
FINISHED |
| Object | Smoky Hill Trail |
—
|
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: Smoky Hill Trail | Statement: [Pike’s Peak Gold Rush, transportRouteUsed, Smoky Hill Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportRouteUsed Context triple: [Pike’s Peak Gold Rush, transportRouteUsed, Smoky Hill Trail]
-
A.
transportNameUsedBy
Indicates that a particular name or designation is used to refer to a specific mode, route, or instance of transport.
-
B.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
C.
currentUseOfRoute
Indicates that a particular route is presently being used for a specific purpose, activity, or traffic flow.
-
D.
hadTransportRoutes
chosen
Indicates that there were established transportation routes or connections between the related entities.
-
E.
usageRoute
Indicates the path, method, or channel through which something is used, applied, or accessed.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 28, 2026, 5:06 p.m.