Triple
T5237545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A20 |
E118258
|
entity |
| Predicate | hasHeavyVehicleUse |
P19599
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [A20, hasHeavyVehicleUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeavyVehicleUse Context triple: [A20, hasHeavyVehicleUse, yes]
-
A.
hasHeavyPassengerTraffic
Indicates that an entity experiences a high volume of passenger movement or usage over a given period.
-
B.
hasHeavyTraffic
Indicates that a location, route, or area is experiencing a high volume of traffic, causing congestion or delays.
-
C.
hasTruckTraffic
chosen
Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
-
D.
hasPrimaryVehicularAccessTo
Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
-
E.
hasVehicleAccess
Indicates that an entity is permitted to use or enter a particular vehicle.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b27990c8190b6a3c24de09c8c18 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.