Triple
T30875296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rehoboth Subprovince |
E786459
|
entity |
| Predicate | hasCrustalAffinity |
P96054
|
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: [Rehoboth Subprovince, hasCrustalAffinity, Kalahari Craton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrustalAffinity Context triple: [Rehoboth Subprovince, hasCrustalAffinity, Kalahari Craton]
-
A.
hasCrustalType
Indicates that an object or location is associated with a specific type or classification of crust (e.g., continental, oceanic).
-
B.
hasCrustalContext
Indicates that something is associated with, situated within, or characterized by a particular geological crustal setting or context.
-
C.
hasCrustalThickness
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
D.
hasTectonicAffinity
chosen
Indicates a relationship where one geological unit or feature shares a common tectonic origin, setting, or structural association with another.
-
E.
containsCraton
Indicates that one geological entity includes or encompasses a craton within its extent or structure.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 8:48 p.m.