Triple
T28855760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydrostachyaceae |
E728728
|
entity |
| Predicate | hasSpecializedMorphology |
P133426
|
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: [Hydrostachyaceae, hasSpecializedMorphology, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecializedMorphology Context triple: [Hydrostachyaceae, hasSpecializedMorphology, true]
-
A.
hasUnusualMorphology
chosen
Indicates that an entity possesses structural or anatomical features that deviate significantly from what is typical or expected for its kind.
-
B.
hasSpecializedOrgan
Indicates that an entity possesses a distinct organ adapted for a particular specialized function or role.
-
C.
hasMorphologyDistinctFrom
Indicates that the morphology (form or structure) of one entity is different from that of another entity.
-
D.
hasMorphologyDescribedIn
Indicates that the morphology of an entity is documented or characterized in a specified source or description.
-
E.
haveSpecializedZooids
Indicates that an organism possesses distinct zooids specialized for particular functions within a colonial or modular body.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 28, 2026, 6:45 a.m.