Triple
T25553140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamuno Border Post |
E640496
|
entity |
| Predicate | timeZoneSideNamibia |
P158866
|
FINISHED |
| Object | Central Africa Time |
E4075
|
NE 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: Central Africa Time | Statement: [Mamuno Border Post, timeZoneSideNamibia, Central Africa Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneSideNamibia Context triple: [Mamuno Border Post, timeZoneSideNamibia, Central Africa Time]
-
A.
timeZoneSideBotswana
Indicates that one entity is located on the Botswana side of a time zone boundary or region.
-
B.
hasTimeZoneOnSouthAfricanSide
Indicates that the referenced entity is located in a region that uses the time zone observed on the South African side of a border or boundary.
-
C.
timeZoneSideEgypt
Indicates that one entity is located on the Egyptian side of a time zone boundary or division.
-
D.
timeZoneOnGibraltarSide
Indicates that the referenced time zone applies specifically to the Gibraltar side of a border, region, or crossing.
-
E.
timeZoneDestination
Indicates the time zone associated with the destination location in a given context or event.
- F. None of above. chosen
Provenance (5 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8c7057881908cca5de0f09a938b |
completed | May 2, 2026, 1:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10ad97c1ac8190b5d2ae6ef8c0f6ec |
completed | May 22, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 3:38 p.m.