Triple
T425164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galloanserae |
E8190
|
entity |
| Predicate | dietDiversity |
P1332
|
FINISHED |
| Object | herbivorous species |
—
|
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: herbivorous species | Statement: [Galloanserae, dietDiversity, herbivorous species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietDiversity Context triple: [Galloanserae, dietDiversity, herbivorous species]
-
A.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
B.
diet
chosen
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
-
C.
metabolicDiversity
Indicates the range and variety of metabolic pathways or processes that an entity can perform or participate in.
-
D.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
E.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.