Triple
T33892233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comté AOC |
E868798
|
entity |
| Predicate | feedingRequirement |
P177879
|
FINISHED |
| Object | cows fed mainly on local pasture and hay |
—
|
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: cows fed mainly on local pasture and hay | Statement: [Comté AOC, feedingRequirement, cows fed mainly on local pasture and hay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedingRequirement Context triple: [Comté AOC, feedingRequirement, cows fed mainly on local pasture and hay]
-
A.
nutritionalRequirement
Indicates that one entity has a need for certain nutrients or dietary conditions that must be met by another entity or resource.
-
B.
bloodMealRequirement
Indicates that an organism requires a blood meal, typically for development, reproduction, or survival.
-
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.
nutritionMode
Indicates the way an entity obtains or processes nutrients for sustenance or growth.
-
E.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
- F. None of above. chosen
Provenance (4 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:48 a.m.