Triple
T425063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesozoic Era |
E8188
|
entity |
| Predicate | oceanLife |
P12485
|
FINISHED |
| Object | diverse marine reptiles such as ichthyosaurs and plesiosaurs |
—
|
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: diverse marine reptiles such as ichthyosaurs and plesiosaurs | Statement: [Mesozoic Era, oceanLife, diverse marine reptiles such as ichthyosaurs and plesiosaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanLife Context triple: [Mesozoic Era, oceanLife, diverse marine reptiles such as ichthyosaurs and plesiosaurs]
-
A.
hasMarineSpecies
chosen
Indicates that an entity contains, supports, or is associated with one or more marine species.
-
B.
marineArea
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
C.
isShallowSea
Indicates that a body of water is a shallow marine area, typically near coasts or continental shelves, rather than deep ocean.
-
D.
enteredOcean
Indicates that an entity moved from land, air, or another medium into the ocean.
-
E.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.