Triple
T30972216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limpopo Belt |
E789129
|
entity |
| Predicate | formsCollisionZoneBetween |
P182260
|
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: [Limpopo Belt, formsCollisionZoneBetween, Kaapvaal Craton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsCollisionZoneBetween Context triple: [Limpopo Belt, formsCollisionZoneBetween, Kaapvaal Craton]
-
A.
collisionZone
Indicates a spatial region within which objects are considered to be in contact or impact with one another, typically used to detect or handle collisions.
-
B.
marksCollisionBetween
Indicates a recorded event or state where two or more entities have come into contact or collided with each other.
-
C.
collidesWith
Indicates that two entities come into contact with each other in space, typically implying an impact or physical intersection of their paths or volumes.
-
D.
collisionFound
Indicates that a collision between two or more entities has been detected.
-
E.
collisionType
Indicates the specific kind or category of collision that occurs between two or more entities.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 29, 2026, 8:55 p.m.