Triple
T29197679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central District of Pakdasht County |
E740171
|
entity |
| Predicate | isMainDistrictOf |
P167404
|
FINISHED |
| Object | Pakdasht County |
—
|
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: Pakdasht County | Statement: [Central District of Pakdasht County, isMainDistrictOf, Pakdasht County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainDistrictOf Context triple: [Central District of Pakdasht County, isMainDistrictOf, Pakdasht County]
-
A.
isInnerDistrictOf
Indicates that one district is geographically or administratively located within and subordinate to another, larger district.
-
B.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
C.
majorCityInDistrict
Indicates that a city serves as a major or principal urban center within a specified district.
-
D.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
E.
geographicallySeparatedDistrictOf
Indicates that one district is a non-contiguous, physically separate part of another district or administrative area.
- F. None of above. chosen
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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 12:04 p.m.