Triple
T25981559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilongwe City Council |
E646083
|
entity |
| Predicate | hasCapitalCityStatusFor |
P83368
|
FINISHED |
| Object | Malawi |
—
|
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: Malawi | Statement: [Lilongwe City Council, hasCapitalCityStatusFor, Malawi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalCityStatusFor Context triple: [Lilongwe City Council, hasCapitalCityStatusFor, Malawi]
-
A.
hasCountryCapitalStatus
chosen
Indicates that a location holds the official status of being the capital city of a specified country.
-
B.
regionCapitalStatus
Indicates that one entity serves as the capital of a specified region or administrative area in relation to another entity.
-
C.
capitalIsNationalCapitalOf
Indicates that one place serves as the official national capital city of a specified country.
-
D.
isCapitalMunicipalityOf
Indicates that a municipality serves as the official capital (administrative center) of a specified larger region, such as a state, province, or country.
-
E.
hasCapitalCityOfContainingUnit
Indicates that a capital city belongs to and is located within a particular larger administrative or territorial unit.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 22, 2026, 8:54 a.m.