Triple
T23971237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chongwe District |
E604237
|
entity |
| Predicate | locatedInNationalCapitalRegion |
P154081
|
FINISHED |
| Object | Lusaka Province |
—
|
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: Lusaka Province | Statement: [Chongwe District, locatedInNationalCapitalRegion, Lusaka Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNationalCapitalRegion Context triple: [Chongwe District, locatedInNationalCapitalRegion, Lusaka Province]
-
A.
locatedInNationCapitalRegion
Indicates that an entity is situated within the capital region of a specific nation.
-
B.
locatedInPrefectureCapitalRegion
Indicates that the subject is geographically situated within the capital region of a given prefecture.
-
C.
locatedInCapital
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
-
D.
locatedInAutonomousRegion
Indicates that one entity is geographically or administratively situated within a self-governing or semi-independent regional territory.
-
E.
locatedInRegionalDistrict
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dc3f088190a55faf6f01ddf4bf |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:25 p.m.