Triple
T4855574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambulacraria |
E108528
|
entity |
| Predicate | hasFeedingMode |
P12462
|
FINISHED |
| Object | suspension feeding in many hemichordates |
—
|
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 in many hemichordates | Statement: [Ambulacraria, hasFeedingMode, suspension feeding in many hemichordates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeedingMode Context triple: [Ambulacraria, hasFeedingMode, suspension feeding in many hemichordates]
-
A.
includesFeedingType
chosen
Indicates that one entity encompasses or specifies a particular type or category of feeding associated with another entity.
-
B.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
-
C.
isFedBy
Indicates that one entity receives nourishment, food, or sustenance from another entity.
-
D.
hasWorkingMode
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
E.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.