Triple
T10559166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atherinomorphae |
E249167
|
entity |
| Predicate | feedingTypeIncludes |
P12462
|
FINISHED |
| Object | omnivores |
—
|
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: omnivores | Statement: [Atherinomorphae, feedingTypeIncludes, omnivores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedingTypeIncludes Context triple: [Atherinomorphae, feedingTypeIncludes, omnivores]
-
A.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
-
B.
includesFeedingType
chosen
Indicates that one entity encompasses or specifies a particular type or category of feeding associated with another entity.
-
C.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
-
D.
feedingSpecialization
Indicates a relationship where an entity is specialized or adapted to feed on a particular type or range of food resources.
-
E.
feedingTraceType
Indicates the specific kind or category of evidence or marks that result from an organism’s feeding activity.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5271e65688190bcf7931373d87f94 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.