Triple
T36154866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimbaza |
E1045697
|
entity |
| Predicate | formerHomelandAssociation |
P149258
|
FINISHED |
| Object | Ciskei |
—
|
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: Ciskei | Statement: [Dimbaza, formerHomelandAssociation, Ciskei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerHomelandAssociation Context triple: [Dimbaza, formerHomelandAssociation, Ciskei]
-
A.
wasHomelandIn
Indicates that a location historically served as the homeland or place of origin for a specified group or entity.
-
B.
hasHomeland
Indicates that an entity considers or recognizes a particular place or region as its homeland or place of origin.
-
C.
isInFormerHomeland
chosen
Indicates that an entity is located within a territory that was once its homeland but is no longer officially recognized as such.
-
D.
servesAsHomelandFor
Indicates that a place functions as the native land, origin, or primary home territory for a particular group or population.
-
E.
homeCountryAssociation
Indicates an association between an entity and the country that is considered its home or primary national affiliation.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a008b8938608190adaccbd720111a18 |
completed | May 10, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_6a008b24baac8190baaaf50c2e9cc6bd |
completed | May 10, 2026, 1:41 p.m. |
Created at: May 3, 2026, 4:08 p.m.