Triple
T2396311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyprinodontiformes |
E47658
|
entity |
| Predicate | containsLivebearingAquariumFish |
P37910
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cyprinodontiformes, containsLivebearingAquariumFish, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLivebearingAquariumFish Context triple: [Cyprinodontiformes, containsLivebearingAquariumFish, true]
-
A.
hasAquariumType
Indicates that an entity is associated with, or classified by, a specific type or category of aquarium.
-
B.
aquariumTrade
Indicates that an entity is involved in the commercial trade or collection of organisms for keeping in aquariums.
-
C.
reproductionInCaptivity
Indicates that an organism reproduces successfully while being kept in a controlled or captive environment rather than in the wild.
-
D.
aquariumSection
Indicates a specific section or area within an aquarium to which something (e.g., an exhibit, organism, or object) is assigned or located.
-
E.
hasMarineSpecies
Indicates that an entity contains, supports, or is associated with one or more marine species.
- F. None of above. chosen
Provenance (4 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c4a8bc819086892a75caac0207 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc664317c8190a6bb5a5065c21bde |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:57 p.m.