Triple
T35279784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe–Mozambique border |
E1018903
|
entity |
| Predicate | currentStates |
P87219
|
FINISHED |
| Object | Republic of Zimbabwe |
—
|
NE NERFINISHED |
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: Republic of Zimbabwe | Statement: [Zimbabwe–Mozambique border, currentStates, Republic of Zimbabwe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentStates Context triple: [Zimbabwe–Mozambique border, currentStates, Republic of Zimbabwe]
-
A.
stateCurrently
Indicates that something is in a particular state or condition at the present moment.
-
B.
modernStateName
chosen
Indicates that an entity is identified by the name of the corresponding modern (current) state or country.
-
C.
primaryStates
Indicates that certain states or conditions are the main or most fundamental ones within a given context or system.
-
D.
contemporaryState
Indicates that two entities exist or occur during the same time period or historical era.
-
E.
compactStates
Indicates that the states in question are geographically small and relatively uniform in shape, lacking extensive protrusions or irregular boundaries.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 3, 2026, 4:03 p.m.