Triple
T28062945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciskei |
E709163
|
entity |
| Predicate | createdAsHomelandFor |
P110910
|
FINISHED |
| Object | Xhosa-speaking people |
—
|
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: Xhosa-speaking people | Statement: [Ciskei, createdAsHomelandFor, Xhosa-speaking people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAsHomelandFor Context triple: [Ciskei, createdAsHomelandFor, Xhosa-speaking people]
-
A.
hasHomeland
Indicates that an entity considers or recognizes a particular place or region as its homeland or place of origin.
-
B.
wasHomelandIn
Indicates that a location historically served as the homeland or place of origin for a specified group or entity.
-
C.
servesAsHomelandFor
chosen
Indicates that a place functions as the native land, origin, or primary home territory for a particular group or population.
-
D.
isInFormerHomeland
Indicates that an entity is located within a territory that was once its homeland but is no longer officially recognized as such.
-
E.
usedToBeHomelandOf
Indicates that a place previously served as the homeland or native territory of a particular group or entity, but no longer does so.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 27, 2026, 8:41 p.m.