Triple
T24463726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blair Atholl Subgroup |
E616906
|
entity |
| Predicate | lithologyType |
P17895
|
FINISHED |
| Object | metasedimentary rocks |
—
|
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: metasedimentary rocks | Statement: [Blair Atholl Subgroup, lithologyType, metasedimentary rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lithologyType Context triple: [Blair Atholl Subgroup, lithologyType, metasedimentary rocks]
-
A.
lithology
chosen
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
B.
lithostratigraphicType
Indicates the specific lithostratigraphic classification or unit type that characterizes a rock body or stratigraphic unit within a geological framework.
-
C.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
D.
lithologyAffected
Indicates that one lithology is influenced, altered, or impacted in some way by another geological process, material, or condition.
-
E.
lithostratigraphicUsage
Indicates how a lithostratigraphic unit name is applied or used within a particular stratigraphic or geological classification context.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298cc60448190a5383d452f563834 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.