Triple
T12496041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Jurassic |
E298686
|
entity |
| Predicate | hasNotableMarineReptiles |
P103109
|
FINISHED |
| Object | 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: plesiosaurs | Statement: [Middle Jurassic, hasNotableMarineReptiles, plesiosaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMarineReptiles Context triple: [Middle Jurassic, hasNotableMarineReptiles, plesiosaurs]
-
A.
hasReptileSpecies
chosen
Indicates that one entity possesses, contains, or is associated with a reptile species as part of its characteristics or composition.
-
B.
hasMarineSpecies
Indicates that an entity contains, supports, or is associated with one or more marine species.
-
C.
hasMarineEcoregion
Indicates that an entity is associated with, or located within, a specific marine ecoregion.
-
D.
hasMarineEcosystem
Indicates that an entity possesses, contains, or is associated with a marine ecosystem as part of its characteristics or environment.
-
E.
hasNotableSea
Indicates that an entity is associated with or contains a sea that is considered notable or significant.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.