Triple
T1411663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusaka |
E31817
|
entity |
| Predicate | becameCapitalOfNorthernRhodesia |
P5604
|
FINISHED |
| Object | 1935 |
—
|
LITERAL 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: 1935 | Statement: [Lusaka, becameCapitalOfNorthernRhodesia, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameCapitalOfNorthernRhodesia Context triple: [Lusaka, becameCapitalOfNorthernRhodesia, 1935]
-
A.
replacedByAsCapitalOfBritishIndia
Indicates that one entity ceased to be the capital of British India and was succeeded in that role by another entity.
-
B.
inauguratedAsCapital
chosen
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
C.
servedAsNationalCapitalFrom
Indicates that a place functioned as the national capital of a country or political entity during a specified time period.
-
D.
wasDeFactoCapitalOf
Indicates that a place functioned in practice as the capital of a political entity, even if it was not officially designated as such.
-
E.
reunifiedAsCapitalInYear
Indicates that an entity regained its status as a capital city in a specified year after a period of not holding that status.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e1da988190bc7c187e193539b6 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.