Triple
T33634948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mbigou |
E861665
|
entity |
| Predicate | locatedInTimeZoneCountry |
P48628
|
FINISHED |
| Object | Gabon |
E8377
|
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: Gabon | Statement: [Mbigou, locatedInTimeZoneCountry, Gabon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTimeZoneCountry Context triple: [Mbigou, locatedInTimeZoneCountry, Gabon]
-
A.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
B.
locatedInTimeZoneDatabaseCountry
chosen
Indicates that the entity is situated in, or associated with, a country as defined in the time zone database.
-
C.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
D.
locatedInTimeZoneUTCOffsetDST
Indicates that an entity exists or operates in a time zone that observes daylight saving time with a specified UTC offset during that DST period.
-
E.
locatedInUtmZone
Indicates that something is situated within a specific Universal Transverse Mercator (UTM) coordinate zone.
- F. None of above.
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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36117b0860819093470f12511de8e9 |
completed | June 20, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:42 a.m.