Triple
T7641477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Pakistan |
E173018
|
entity |
| Predicate | borderDirectionWithinCountry |
P70148
|
FINISHED |
| Object | southern part of Pakistan |
—
|
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: southern part of Pakistan | Statement: [Southern Pakistan, borderDirectionWithinCountry, southern part of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirectionWithinCountry Context triple: [Southern Pakistan, borderDirectionWithinCountry, southern part of Pakistan]
-
A.
borderCountrySide
chosen
Indicates that one country shares a land border with the side or region of another country.
-
B.
countryBorderDirection
Indicates the cardinal or relative direction in which one country lies in relation to the border it shares with another country.
-
C.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
D.
hasBorderMeetingCountry
Indicates that one country shares a land or maritime border with another country.
-
E.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6facefbe08190882bd76cf3cd605e |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.