Triple
T11540249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zero Point Interchange, Islamabad |
E273654
|
entity |
| Predicate | roadDirectionServed |
P44884
|
FINISHED |
| Object | traffic to central Islamabad |
—
|
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: traffic to central Islamabad | Statement: [Zero Point Interchange, Islamabad, roadDirectionServed, traffic to central Islamabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDirectionServed Context triple: [Zero Point Interchange, Islamabad, roadDirectionServed, traffic to central Islamabad]
-
A.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
B.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
C.
hasStreetDirection
chosen
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
-
D.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
E.
roadDirectionConvention
Indicates the customary rule in a place for which side of the road vehicles are expected to drive on.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886deed5c81908e5c38156064f882 |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.