Triple
T2916341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colombian Basin |
E78615
|
entity |
| Predicate | hasSedimentaryCover |
P18668
|
FINISHED |
| Object | thick pelagic 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: thick pelagic sediments | Statement: [Colombian Basin, hasSedimentaryCover, thick pelagic sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSedimentaryCover Context triple: [Colombian Basin, hasSedimentaryCover, thick pelagic sediments]
-
A.
hasSedimentsThat
chosen
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
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.
hasSedimentLoad
Indicates that one entity (typically a water body or flow) carries or transports a certain amount or type of sediment associated with another entity.
-
D.
hasCrustalThickness
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
E.
hasGeologicalEvidenceOf
Indicates that there is geological data or features supporting the existence, occurrence, or impact of a specified phenomenon or event.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:53 p.m.