Triple
T6981564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moine Thrust Belt |
E161857
|
entity |
| Predicate | lithologyInvolved |
P17895
|
FINISHED |
| Object | metamorphic 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: metamorphic rocks | Statement: [Moine Thrust Belt, lithologyInvolved, metamorphic rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lithologyInvolved Context triple: [Moine Thrust Belt, lithologyInvolved, metamorphic rocks]
-
A.
lithology
chosen
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
B.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
C.
geologyIncludes
Indicates that one geological entity contains, encompasses, or has as a component another geological entity.
-
D.
geologicalStatus
Indicates the current geological condition or classification of an entity, such as its formation state, activity level, or structural status within the Earth’s crust.
-
E.
lithosphereType
Indicates the classification of a lithospheric unit according to its type (e.g., oceanic, continental, or other defined categories).
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6d3f3c8190b0121f7934440c34 |
completed | March 27, 2026, 7:33 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.