Triple
T19004785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Embayment |
E465050
|
entity |
| Predicate | maximumSedimentThickness |
P77073
|
FINISHED |
| Object | over 3000 meters |
—
|
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: over 3000 meters | Statement: [Mississippi Embayment, maximumSedimentThickness, over 3000 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSedimentThickness Context triple: [Mississippi Embayment, maximumSedimentThickness, over 3000 meters]
-
A.
sedimentaryCoverThickness
chosen
Indicates the thickness or depth of the sedimentary cover layer overlying a given geological unit or surface.
-
B.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
-
C.
hasStratigraphicThickness
Indicates the measured vertical thickness or depth extent of a stratigraphic unit or layer.
-
D.
maximumHeightAboveSeafloor
Indicates the greatest vertical distance between an object or feature and the seafloor beneath it.
-
E.
typicalSedimentSizeRange
Indicates the usual range of sediment particle sizes associated with an entity or environment.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a3db9c8190a1bf0228e360a6e0 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.