Triple
T16551476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydractinia echinata |
E402080
|
entity |
| Predicate | usedAsModelOrganismFor |
P32525
|
FINISHED |
| Object | regeneration |
—
|
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: regeneration | Statement: [Hydractinia echinata, usedAsModelOrganismFor, regeneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsModelOrganismFor Context triple: [Hydractinia echinata, usedAsModelOrganismFor, regeneration]
-
A.
notableModelOrganism
Indicates that an organism is widely recognized and frequently used as a standard or reference model for scientific research or experimentation.
-
B.
isModelOrganism
chosen
Indicates that one organism is used as a representative experimental system for studying biological processes relevant to other organisms.
-
C.
studiedOrganism
Indicates that an entity conducted study or research on a particular organism.
-
D.
containsModelOrganisms
Indicates that one entity includes or incorporates model organisms as part of its contents or composition.
-
E.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc56f9081908bb8f6433a1a688d |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.