Triple
T9143215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siberian Craton |
E219382
|
entity |
| Predicate | formsBasementUnder |
P65586
|
FINISHED |
| Object | much of eastern Siberia |
—
|
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: much of eastern Siberia | Statement: [Siberian Craton, formsBasementUnder, much of eastern Siberia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBasementUnder Context triple: [Siberian Craton, formsBasementUnder, much of eastern Siberia]
-
A.
formsBasementFor
chosen
Indicates that one entity serves as the foundational or lowest structural layer upon which another entity is built or supported.
-
B.
basementType
Indicates the type or classification of a building’s basement as defined in the relationship.
-
C.
hasBasement
Indicates that a building or structure includes a basement level as part of its physical layout.
-
D.
hasBasementUse
Indicates that a building or structure’s basement is used for a specified purpose or function.
-
E.
numberOfBasementLevels
Indicates the total count of basement levels associated with a given structure or property.
- 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.