Triple
T24376254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Africa–Mozambique border |
E614481
|
entity |
| Predicate | hasTimeZoneOnMozambicanSide |
P3413
|
FINISHED |
| Object | UTC+2 |
—
|
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: UTC+2 | Statement: [South Africa–Mozambique border, hasTimeZoneOnMozambicanSide, UTC+2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeZoneOnMozambicanSide Context triple: [South Africa–Mozambique border, hasTimeZoneOnMozambicanSide, UTC+2]
-
A.
hasTimeZoneNote
Indicates that there is an associated note or annotation providing additional information or clarification about a time zone.
-
B.
hasTimeZoneDifferenceAlongBorder
Indicates that two adjacent regions share a border across which their official time zones differ.
-
C.
linkedToMainlandTimeZone
Indicates that an entity’s time zone is synchronized with or derived from the primary mainland time zone of a region or country.
-
D.
hasTimeZones
chosen
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
timeZoneOnMexicanSide
Indicates that the referenced time zone applies specifically to the Mexican side of a border or boundary.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d73c0c8190b80e257845a04c57 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.