Triple
T37815324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PWV conurbation |
E942757
|
entity |
| Predicate | historicalNameUsedBefore |
P145623
|
FINISHED |
| Object | Gauteng Province creation |
—
|
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: Gauteng Province creation | Statement: [PWV conurbation, historicalNameUsedBefore, Gauteng Province creation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameUsedBefore Context triple: [PWV conurbation, historicalNameUsedBefore, Gauteng Province creation]
-
A.
historicalNameUsedIn
chosen
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
B.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
C.
historicalNameUntil
Indicates that an entity bore a particular historical name up to a specified point in time, after which that name was no longer used.
-
D.
isHistoricalName
Indicates that a given name is a former or past designation historically used for an entity.
-
E.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01beacf8a88190ac643a75c7a0efc4 |
completed | May 11, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_6a01be152c8c8190bb19d64a683e2aae |
completed | May 11, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:19 p.m.