Triple
T30875339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magondi Belt |
E786461
|
entity |
| Predicate | locatedOnCratonMargin |
P203137
|
FINISHED |
| Object | Kalahari Craton |
—
|
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: Kalahari Craton | Statement: [Magondi Belt, locatedOnCratonMargin, Kalahari Craton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnCratonMargin Context triple: [Magondi Belt, locatedOnCratonMargin, Kalahari Craton]
-
A.
containsCraton
Indicates that one geological entity includes or encompasses a craton within its extent or structure.
-
B.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
-
C.
continentMargin
Indicates that one entity lies along or forms the boundary region at the edge of a continental landmass relative to another entity.
-
D.
locatedOnTectonicPlate
Indicates that one entity (typically a geographic region or feature) lies upon or is situated on the tectonic plate represented by the other entity.
-
E.
hasOceanicCrustAlong
Indicates that an entity possesses or is characterized by oceanic crust extending along a specified boundary, feature, or region.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0127c36dc08190b07765756b3d0e1b |
completed | May 11, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_6a0125ef57208190be5b5e761fcae981 |
completed | May 11, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_6a0127c27a888190a530763f4216e7d5 |
completed | May 11, 2026, 12:50 a.m. |
Created at: April 29, 2026, 8:48 p.m.