Triple
T13852393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazinga National Park |
E332976
|
entity |
| Predicate | hasCurrentNameSince |
P70850
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Kazinga National Park, hasCurrentNameSince, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentNameSince Context triple: [Kazinga National Park, hasCurrentNameSince, 1954]
-
A.
usesNameSince
Indicates that an entity has been using a particular name continuously starting from a specified point in time.
-
B.
nameUsedSince
chosen
Indicates that a particular name has been in use for an entity starting from a specified point in time.
-
C.
hasNameBeforeChange
Indicates that an entity is associated with the name it had prior to some change or renaming event.
-
D.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
E.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02da9460819093a3ec5a3c62ea81 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.