Triple
T5481865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Star |
E123483
|
entity |
| Predicate | routeAcross |
P30397
|
FINISHED |
| Object | northern United States |
—
|
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: northern United States | Statement: [Western Star, routeAcross, northern United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAcross Context triple: [Western Star, routeAcross, northern United States]
-
A.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
B.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
C.
roadTraverses
chosen
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
D.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
E.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.