Triple
T428314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Cape |
E9657
|
entity |
| Predicate | establishedAsProvince |
P5762
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Western Cape, establishedAsProvince, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsProvince Context triple: [Western Cape, establishedAsProvince, 1994]
-
A.
establishedAs
chosen
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
B.
statehoodYear
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
C.
province
Indicates that one entity is an administrative subdivision or region (a province) governed by or belonging to another, typically larger, political or territorial entity.
-
D.
capitalOfProvincePreviouslyLocatedOn
Indicates that an entity serves or served as the capital city of a province that was formerly situated in a specified location.
-
E.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeecb64c81908c5c83ef7c0181e6 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd7a3608190b8785c7b7205f6c1 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.