Triple
T22475332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okapi Wildlife Reserve |
E555613
|
entity |
| Predicate | designatedAsReserveIn |
P85100
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Okapi Wildlife Reserve, designatedAsReserveIn, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedAsReserveIn Context triple: [Okapi Wildlife Reserve, designatedAsReserveIn, 1992]
-
A.
establishedAsReserve
chosen
Indicates that an area or resource has been formally designated and set aside as a reserve for protection or special management.
-
B.
isOnReserve
Indicates that an entity is currently set aside or held in reserve, rather than being in regular or active use.
-
C.
placedInReserve
Indicates that an entity has been set aside or allocated into a reserve, rather than being used or kept in general circulation.
-
D.
isPrimaryReserveOf
Indicates that one entity serves as the main or principal reserve (backup or stored resource) for another entity.
-
E.
isStrategicReserveFor
Indicates that one entity is held or designated as a backup or contingency resource to be used strategically in support of another 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be3930c8190ba967196df7e083f |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.