Triple
T6991076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaapvaal Craton |
E162085
|
entity |
| Predicate | lithosphericThickness |
P74321
|
FINISHED |
| Object | up to about 200–250 km |
—
|
LITERAL FINISHED |
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: up to about 200–250 km | Statement: [Kaapvaal Craton, lithosphericThickness, up to about 200–250 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lithosphericThickness Context triple: [Kaapvaal Craton, lithosphericThickness, up to about 200–250 km]
-
A.
lithosphereType
Indicates the classification of a lithospheric unit according to its type (e.g., oceanic, continental, or other defined categories).
-
B.
hasCrustalThickness
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
C.
crustalComposition
Indicates the type and proportion of materials that make up a planet or moon’s outer solid layer (its crust).
-
D.
ageOfSubductingPlate
Indicates the age of a tectonic plate at the time and location where it is being subducted beneath another plate.
-
E.
surfaceRegolithDepth_m
Indicates the measured thickness of the loose surface regolith layer at a location, expressed in meters.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc08758819083d36a1fc0463b27 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dbbc00fc8190a18221524b774021 |
completed | March 27, 2026, 7:34 p.m. |
Created at: March 27, 2026, 2:32 p.m.