Triple
T16184999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matiari–Lahore HVDC transmission line |
E392777
|
entity |
| Predicate | toRegion |
P51005
|
FINISHED |
| Object | northern Pakistan demand centers |
—
|
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: northern Pakistan demand centers | Statement: [Matiari–Lahore HVDC transmission line, toRegion, northern Pakistan demand centers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toRegion Context triple: [Matiari–Lahore HVDC transmission line, toRegion, northern Pakistan demand centers]
-
A.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
B.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
C.
routeRegion
chosen
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22060dcf88190b7c662946a5f0191 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.