Triple
T2796205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Late Jurassic |
E53042
|
entity |
| Predicate | oceanCoverage |
P2021
|
FINISHED |
| Object | extensive shallow epicontinental seas |
—
|
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: extensive shallow epicontinental seas | Statement: [Late Jurassic, oceanCoverage, extensive shallow epicontinental seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanCoverage Context triple: [Late Jurassic, oceanCoverage, extensive shallow epicontinental seas]
-
A.
hasOceanCoverage
chosen
Indicates that a specified area or region is covered by ocean to a certain extent or proportion.
-
B.
oceanicPortion
Indicates that one entity is a part or segment of an ocean or oceanic area in relation to another entity.
-
C.
isMostlyOceanic
Indicates that something consists predominantly of ocean or sea areas rather than land.
-
D.
coversFractionOfWorldOceanArea
Indicates that a specified entity accounts for a given fraction of the total surface area of the world’s oceans.
-
E.
oceanBasin
Indicates a relationship where a geographic or marine feature is located within, or is part of, a specific ocean basin.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddef754081908e6218dc2208e0fd |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.