Triple
T28062959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciskei |
E709163
|
entity |
| Predicate | integratedIntoNewProvinces |
P124980
|
FINISHED |
| Object | Eastern Cape |
—
|
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: Eastern Cape | Statement: [Ciskei, integratedIntoNewProvinces, Eastern Cape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedIntoNewProvinces Context triple: [Ciskei, integratedIntoNewProvinces, Eastern Cape]
-
A.
hasTerritoryReorganizedInto
chosen
Indicates that an entity’s territorial boundaries or administrative divisions have been restructured to form another specified territory.
-
B.
partOfAdministrativeDivisionReform
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
C.
joinedAsProvince
Indicates that an entity became part of a larger political or administrative unit with the status of a province.
-
D.
wasDividedFrom
Indicates that one entity was separated or split off from another entity, resulting in two distinct parts or groups.
-
E.
territorialChange
Indicates a change in control or ownership of geographic territory from one entity to another, often as a result of political, legal, or military events.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 8:41 p.m.