Triple
T21373745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakesdale, Washington |
E527137
|
entity |
| Predicate | transportationTypeNearby |
P1379
|
FINISHED |
| Object | rural highways |
—
|
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: rural highways | Statement: [Oakesdale, Washington, transportationTypeNearby, rural highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationTypeNearby Context triple: [Oakesdale, Washington, transportationTypeNearby, rural highways]
-
A.
transportationNearby
Indicates that there is a transportation facility or service located close to the referenced entity.
-
B.
operatorOfNearbyTransit
Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
-
C.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
D.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
-
E.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0b248508190aebeb671e55198da |
completed | April 22, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:10 p.m.