Triple
T37698925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shahrah-e-Faisal |
E939003
|
entity |
| Predicate | isMainArteryOf |
P18708
|
FINISHED |
| Object | Karachi road network |
—
|
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: Karachi road network | Statement: [Shahrah-e-Faisal, isMainArteryOf, Karachi road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainArteryOf Context triple: [Shahrah-e-Faisal, isMainArteryOf, Karachi road network]
-
A.
isMajorArterialFor
chosen
Indicates that something functions as a primary high-capacity route or conduit serving as a main channel for movement, flow, or traffic for something else.
-
B.
isMainRoad
Indicates that a road serves as a primary or major thoroughfare within a transportation network.
-
C.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
D.
hasArterialRoad
Indicates that one location or area is connected to or served by a major arterial road used for primary traffic flow.
-
E.
arterialRoad
Indicates that a road functions as a primary high-capacity route that channels major traffic flows between different areas of a transport network.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.