Triple
T9672378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cetancodonta |
E234058
|
entity |
| Predicate | containsAquaticMammals |
P83094
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cetancodonta, containsAquaticMammals, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAquaticMammals Context triple: [Cetancodonta, containsAquaticMammals, yes]
-
A.
containsAquaticMembers
chosen
Indicates that a group or collection includes one or more members that live in or are adapted to aquatic environments.
-
B.
hasMarineSpecies
Indicates that an entity contains, supports, or is associated with one or more marine species.
-
C.
hasAquaticEcosystem
Indicates that an entity possesses, contains, or is associated with an ecosystem primarily based in water (such as rivers, lakes, wetlands, or oceans).
-
D.
hasMarineEcosystem
Indicates that an entity possesses, contains, or is associated with a marine ecosystem as part of its characteristics or environment.
-
E.
hasMarineEcoregion
Indicates that an entity is associated with, or located within, a specific marine ecoregion.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6aa01c819083fc758470096ec2 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.