Triple
T32300247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Char Burjak District |
E825216
|
entity |
| Predicate | locatedInProvinceBorderArea |
P162361
|
FINISHED |
| Object | Nimruz–Iran border |
E801169
|
NE 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: Nimruz–Iran border | Statement: [Char Burjak District, locatedInProvinceBorderArea, Nimruz–Iran border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInProvinceBorderArea Context triple: [Char Burjak District, locatedInProvinceBorderArea, Nimruz–Iran border]
-
A.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
-
B.
isBorderDistrict
chosen
Indicates that a district is located along and directly borders the boundary of a larger administrative region or country.
-
C.
positionWithinProvince
Indicates that one entity’s location lies inside the geographic or administrative boundaries of a specified province.
-
D.
borderingCountryOfItsProvince
Indicates that one country shares a land border with the country to which a given province belongs.
-
E.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
- F. None of above.
Provenance (4 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a022c5269888190944314074aedfe73 |
completed | May 11, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a30570a2f2881908f27137c9bc702c1 |
completed | June 15, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a02286020308190b238183f7ba2065f |
completed | May 11, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:45 a.m.