Triple
T10295564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe–Zambia border |
E241475
|
entity |
| Predicate | timeAsInternalBoundaryStart |
P92965
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [Zimbabwe–Zambia border, timeAsInternalBoundaryStart, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAsInternalBoundaryStart Context triple: [Zimbabwe–Zambia border, timeAsInternalBoundaryStart, 1953]
-
A.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
B.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
C.
startTimeAsCCPBase
Indicates that the referenced time value serves as the initial or baseline start time for an event or process within the CCP (Control/Command/Configuration) context.
-
D.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
-
E.
timeAsCapitalStart
Indicates the point in time when a location first became the capital of a political or administrative entity.
- F. None of above. chosen
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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2ea9b3c8190b11518b259d5825c |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d29d7cf08190acd70cee634c5cdb |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:43 a.m.