Triple
T22657047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DF Malan Airport |
E559253
|
entity |
| Predicate | successorNameInUseSince |
P149084
|
FINISHED |
| Object | post-1994 democratic era |
—
|
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: post-1994 democratic era | Statement: [DF Malan Airport, successorNameInUseSince, post-1994 democratic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorNameInUseSince Context triple: [DF Malan Airport, successorNameInUseSince, post-1994 democratic era]
-
A.
hasOfficialSuccessorName
Indicates that an entity has an officially designated successor identified by a specific name.
-
B.
successorNameChange
Indicates that an entity’s name has been changed to a new name that succeeds or replaces its previous name.
-
C.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
D.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
-
E.
namedSuccessor
Indicates that one entity has been explicitly designated as the successor or heir to another entity.
- F. None of above. chosen
Provenance (4 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765c62bc8190b3fcde76d6b6dfb6 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:06 p.m.