Triple
T28049145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunter Sandstone |
E708771
|
entity |
| Predicate | stratigraphicPositionBelow |
P35989
|
FINISHED |
| Object | Muschelkalk |
—
|
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: Muschelkalk | Statement: [Bunter Sandstone, stratigraphicPositionBelow, Muschelkalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stratigraphicPositionBelow Context triple: [Bunter Sandstone, stratigraphicPositionBelow, Muschelkalk]
-
A.
hasStratigraphicPosition
chosen
Indicates the relative position of one geological layer or unit within a stratigraphic sequence in relation to another.
-
B.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
C.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
D.
appearsBelow
Indicates that one entity is visually or spatially positioned lower than another in a layout, sequence, or display.
-
E.
stratigraphicSuperunitOf
Indicates that one stratigraphic unit is a higher-level or more encompassing unit that contains or groups together another stratigraphic unit within a geological stratigraphic hierarchy.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 8:31 p.m.