Triple
T4002015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthozoa |
E89434
|
entity |
| Predicate | feedingMechanism |
P12462
|
FINISHED |
| Object | suspension feeding |
—
|
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: suspension feeding | Statement: [Anthozoa, feedingMechanism, suspension feeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedingMechanism Context triple: [Anthozoa, feedingMechanism, suspension feeding]
-
A.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
-
B.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
-
C.
feederSystem
Indicates a system or mechanism that supplies or feeds resources, materials, or inputs into another process, component, or structure.
-
D.
includesFeedingType
chosen
Indicates that one entity encompasses or specifies a particular type or category of feeding associated with another entity.
-
E.
feedConversionEfficiency
Indicates how efficiently input feed is converted into desired output (such as growth, product, or energy) in a biological or production system.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.