Triple
T33116700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mizan District |
E847476
|
entity |
| Predicate | borderingDistrictOfZabulProvince |
P120977
|
FINISHED |
| Object | Shah Joy District |
—
|
NE NERFINISHED |
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: Shah Joy District | Statement: [Mizan District, borderingDistrictOfZabulProvince, Shah Joy District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingDistrictOfZabulProvince Context triple: [Mizan District, borderingDistrictOfZabulProvince, Shah Joy District]
-
A.
borderingDistrictInDaykundi
Indicates that one district shares a common boundary with another district within the Daykundi region.
-
B.
borderingCountryOfItsProvince
Indicates that one country shares a land border with the country to which a given province belongs.
-
C.
isBorderDistrict
Indicates that a district is located along and directly borders the boundary of a larger administrative region or country.
-
D.
borderingBhutaneseDistricts
Indicates that the specified Bhutanese districts share a common boundary with each other.
-
E.
borderingAdministrativeTerritorialEntity
chosen
Indicates that one administrative territorial entity shares a common boundary with another administrative territorial entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 1, 2026, 1:27 a.m.