Triple
T27881267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bemba Kingdom |
E705094
|
entity |
| Predicate | todayRecognizedAs |
P58651
|
FINISHED |
| Object | traditional authority in Zambia |
—
|
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: traditional authority in Zambia | Statement: [Bemba Kingdom, todayRecognizedAs, traditional authority in Zambia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: todayRecognizedAs Context triple: [Bemba Kingdom, todayRecognizedAs, traditional authority in Zambia]
-
A.
todayRememberedAs
Indicates that an event, person, or occurrence is being commemorated or recalled on the present day.
-
B.
oftenRecognizedBy
Indicates that one entity is frequently identified, acknowledged, or noticed by another entity.
-
C.
knownTodayAs
chosen
Indicates that an entity is currently referred to or recognized by a particular name or designation in the present time.
-
D.
peopleRecognizedAs
Indicates that certain individuals are acknowledged or identified as having a particular status, role, or identity in relation to something or someone.
-
E.
isCelebratedAs
Indicates that an entity is recognized, honored, or regarded in a particular role, status, or capacity.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63982891c8190b29054f8c0276342 |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:30 p.m.