Triple
T16551479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydractinia echinata |
E402080
|
entity |
| Predicate | hasAllorecognitionSystem |
P15551
|
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, hasAllorecognitionSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllorecognitionSystem Context triple: [Hydractinia echinata, hasAllorecognitionSystem, true]
-
A.
hasProcessOfRecognition
Indicates that one entity is involved in or characterized by a process of recognizing, identifying, or acknowledging another entity or condition.
-
B.
hasFaceUnlock
Indicates that an entity supports or is equipped with a facial recognition–based unlocking feature.
-
C.
canRecognize
chosen
Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
-
D.
hasRecognitionList
Indicates that an entity is associated with a specific list detailing recognitions, awards, or honors it has received.
-
E.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
- 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.