Triple
T25497612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ventersdorp Supergroup |
E639021
|
entity |
| Predicate | locatedOnCraton |
P33297
|
FINISHED |
| Object | Kaapvaal 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: Kaapvaal Craton | Statement: [Ventersdorp Supergroup, locatedOnCraton, Kaapvaal Craton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnCraton Context triple: [Ventersdorp Supergroup, locatedOnCraton, Kaapvaal Craton]
-
A.
containsCraton
chosen
Indicates that one geological entity includes or encompasses a craton within its extent or structure.
-
B.
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.
-
C.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
-
D.
locatedOnTerrain
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
E.
locatedInCrater
Indicates that one entity is situated within the boundaries of a specific crater.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 21, 2026, 2:41 p.m.