Triple
T964598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaviza |
E20809
|
entity |
| Predicate | roadConnectionDirection |
P4069
|
FINISHED |
| Object | north toward Panama City |
—
|
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: north toward Panama City | Statement: [Yaviza, roadConnectionDirection, north toward Panama City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadConnectionDirection Context triple: [Yaviza, roadConnectionDirection, north toward Panama City]
-
A.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
B.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
C.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
D.
hasTrafficDirection
chosen
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
E.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4303e5881909d101d11f9732c75 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.