Triple
T30068576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Saxony Basin |
E764109
|
entity |
| Predicate | hasBasinFillThickness |
P169229
|
FINISHED |
| Object | several kilometers of sediment |
—
|
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: several kilometers of sediment | Statement: [Lower Saxony Basin, hasBasinFillThickness, several kilometers of sediment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasinFillThickness Context triple: [Lower Saxony Basin, hasBasinFillThickness, several kilometers of sediment]
-
A.
isPartOfBasinFill
Indicates that a geological unit or deposit belongs to, and was formed as part of, the sedimentary fill within a structural or depositional basin.
-
B.
basinFill
Indicates that a basin or low-lying area becomes filled with material, such as water or sediment, as a result of accumulation over time.
-
C.
hasBasinFunction
Indicates that something serves the role or performs the function of a basin, such as collecting, holding, or draining water or other substances.
-
D.
hasApproximateAverageThickness
chosen
Indicates that an entity possesses a thickness value that is an estimated or typical average rather than an exact measurement.
-
E.
hasThicknessRange
Indicates that an entity is associated with a minimum and maximum thickness value defining the range of its thickness.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 7 p.m.