Triple
T36464266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lactoria cornuta |
E898380
|
entity |
| Predicate | aquariumRisk |
P185754
|
FINISHED |
| Object | toxin release can kill tankmates |
—
|
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: toxin release can kill tankmates | Statement: [Lactoria cornuta, aquariumRisk, toxin release can kill tankmates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aquariumRisk Context triple: [Lactoria cornuta, aquariumRisk, toxin release can kill tankmates]
-
A.
aquariumSection
Indicates a specific section or area within an aquarium to which something (e.g., an exhibit, organism, or object) is assigned or located.
-
B.
aquariumTrade
Indicates that an entity is involved in the commercial trade or collection of organisms for keeping in aquariums.
-
C.
containsAquariumFish
Indicates that one entity includes or holds aquarium fish within it.
-
D.
reefCompatibility
Indicates whether an entity can safely coexist with typical reef organisms without causing harm or disruption.
-
E.
aquariumBehavior
Indicates behavior or actions performed by an entity within the context of an aquarium environment.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.