Triple
T9143207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siberian Craton |
E219382
|
entity |
| Predicate | hasMantleRoot |
P20812
|
FINISHED |
| Object | thick lithospheric mantle keel |
—
|
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: thick lithospheric mantle keel | Statement: [Siberian Craton, hasMantleRoot, thick lithospheric mantle keel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMantleRoot Context triple: [Siberian Craton, hasMantleRoot, thick lithospheric mantle keel]
-
A.
hasMaintenanceBase
Indicates that an entity is supported, serviced, or maintained at a specific base or maintenance facility.
-
B.
mantleType
chosen
Indicates the type or classification of a mantle associated with an entity, specifying what kind of mantle it has.
-
C.
hasWellAtRoot
Indicates that an entity possesses or has a well located at its root or base.
-
D.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
E.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8f5f740819098236ada5b95889d |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:19 p.m.