Triple
T809597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skagway |
E17513
|
entity |
| Predicate | wasMajorRouteFor |
P18708
|
FINISHED |
| Object | prospectors traveling to Yukon goldfields |
—
|
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: prospectors traveling to Yukon goldfields | Statement: [Skagway, wasMajorRouteFor, prospectors traveling to Yukon goldfields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorRouteFor Context triple: [Skagway, wasMajorRouteFor, prospectors traveling to Yukon goldfields]
-
A.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
B.
isMajorArterialFor
chosen
Indicates that something functions as a primary high-capacity route or conduit serving as a main channel for movement, flow, or traffic for something else.
-
C.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
D.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
-
E.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.