Triple
T16551493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydractinia echinata |
E402080
|
entity |
| Predicate | hasPolymorphicZooids |
P122185
|
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: [Hydractinia echinata, hasPolymorphicZooids, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolymorphicZooids Context triple: [Hydractinia echinata, hasPolymorphicZooids, true]
-
A.
haveSpecializedZooids
chosen
Indicates that an organism possesses distinct zooids specialized for particular functions within a colonial or modular body.
-
B.
hasZoo
Indicates that one entity possesses, operates, or is associated with a zoo.
-
C.
polymorphic
Indicates that an entity can take on multiple distinct forms or types while maintaining a common interface or role in a relationship or action.
-
D.
hasWorkerPolymorphism
Indicates that an entity supports multiple interchangeable worker implementations or roles that can perform the same task in different ways.
-
E.
zooCode
Indicates a relationship where an entity is assigned or associated with a specific zoo identification code.
- 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.