Triple
T30875462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Damara Belt |
E786464
|
entity |
| Predicate | separatesCratons |
P9693
|
FINISHED |
| Object | Congo 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: Congo Craton | Statement: [Damara Belt, separatesCratons, Congo Craton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesCratons Context triple: [Damara Belt, separatesCratons, Congo Craton]
-
A.
separatesRockTerranes
chosen
Indicates a geological boundary or feature that divides or distinguishes different rock terranes from one another.
-
B.
containsCraton
Indicates that one geological entity includes or encompasses a craton within its extent or structure.
-
C.
separatesLandmasses
Indicates that one entity (typically a physical feature like water or terrain) divides or creates a boundary between two or more landmasses.
-
D.
separatedContinents
Indicates that the related entities are located on different continents, with a geographic separation between them.
-
E.
separatedFromSahulShelfBy
Indicates that one entity is divided or kept apart from the Sahul continental shelf by some intervening geographic or physical barrier.
- 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_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:48 p.m.