Triple
T31823390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falkland Plateau |
E812323
|
entity |
| Predicate | hasSedimentaryBasins |
P60963
|
FINISHED |
| Object | Mesozoic–Cenozoic basins |
—
|
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: Mesozoic–Cenozoic basins | Statement: [Falkland Plateau, hasSedimentaryBasins, Mesozoic–Cenozoic basins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSedimentaryBasins Context triple: [Falkland Plateau, hasSedimentaryBasins, Mesozoic–Cenozoic basins]
-
A.
hasSedimentaryBasin
chosen
Indicates that a geological region or area contains or is associated with a sedimentary basin.
-
B.
hasWaterBasins
Indicates that one entity possesses, contains, or includes one or more water basins in relation to another entity.
-
C.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
D.
hasHydrocarbonTraps
Indicates the presence of geological structures or conditions that can accumulate and retain hydrocarbons such as oil or gas.
-
E.
hasHydrocarbonLakes
Indicates that the subject possesses or contains lakes composed primarily of liquid hydrocarbons rather than water.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: April 30, 2026, 11:46 p.m.