Triple
T23672056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Africa–Lesotho border |
E584756
|
entity |
| Predicate | hasAdjacentSouthAfricanProvince |
P91381
|
FINISHED |
| Object | Free State |
—
|
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: Free State | Statement: [South Africa–Lesotho border, hasAdjacentSouthAfricanProvince, Free State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentSouthAfricanProvince Context triple: [South Africa–Lesotho border, hasAdjacentSouthAfricanProvince, Free State]
-
A.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
B.
hasProvincialCapitalWithin
Indicates that a province’s official capital city is geographically located within the boundaries of a specified area or region.
-
C.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
D.
hasSisterProvince
Indicates that two provinces are related to each other as sister provinces, typically through a formal partnership or cooperative relationship.
-
E.
hasAdjacentJurisdiction
chosen
Indicates that one jurisdiction directly borders or is immediately next to another jurisdiction.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b41002f881908cd744ed44b70f5d |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.