Triple
T8020423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thuringian Basin |
E186725
|
entity |
| Predicate | dominantRocks |
P4015
|
FINISHED |
| Object | Triassic sediments |
—
|
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: Triassic sediments | Statement: [Thuringian Basin, dominantRocks, Triassic sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantRocks Context triple: [Thuringian Basin, dominantRocks, Triassic sediments]
-
A.
geologicEraDominantRocks
Indicates that a particular type or group of rocks is the most characteristic or prevalent during a given geologic era.
-
B.
commonRockUnit
Indicates that two or more geological features share the same rock unit or lithostratigraphic layer.
-
C.
centralRockName
Indicates that an entity has a specific name assigned to its central rock or primary rock feature.
-
D.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
E.
geologicalFormation
chosen
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8d90488190b57d1e748e272061 |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.