Triple
T4409824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millstone Grit |
E94826
|
entity |
| Predicate | containsLithology |
P17895
|
FINISHED |
| Object | conglomerate |
—
|
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: conglomerate | Statement: [Millstone Grit, containsLithology, conglomerate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLithology Context triple: [Millstone Grit, containsLithology, conglomerate]
-
A.
lithology
chosen
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
B.
hasStratigraphicFeature
Indicates a relationship in which a geological unit, site, or context contains, exhibits, or is associated with a particular stratigraphic feature (such as a layer, horizon, or boundary) within its stratigraphic sequence.
-
C.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
D.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
E.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3548e24d08190a38c0bcd4b6ad571 |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.