Triple
T31196031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwestern Afghanistan |
E795321
|
entity |
| Predicate | administrativeCenterInRegion |
P192306
|
FINISHED |
| Object | Lashkar Gah |
—
|
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: Lashkar Gah | Statement: [Southwestern Afghanistan, administrativeCenterInRegion, Lashkar Gah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeCenterInRegion Context triple: [Southwestern Afghanistan, administrativeCenterInRegion, Lashkar Gah]
-
A.
administrativeCenterRegion
Indicates that a region serves as the administrative center or seat of government for another territorial unit.
-
B.
capitalLocatedInRegion
Indicates that a capital city is geographically situated within a specific region.
-
C.
capitalOfReferencedRegion
Indicates that one entity serves as the capital city or administrative center of the region referenced by another entity.
-
D.
capitalCityOfRegion
Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
-
E.
capitalLocationRegion
Indicates that a location serves as the capital city or administrative center of a specified region.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 29, 2026, 9:09 p.m.