Triple
T25050412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AOC Bresse chicken |
E627361
|
entity |
| Predicate | feedRequirement |
P122676
|
FINISHED |
| Object | local cereals |
—
|
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: local cereals | Statement: [AOC Bresse chicken, feedRequirement, local cereals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedRequirement Context triple: [AOC Bresse chicken, feedRequirement, local cereals]
-
A.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
-
B.
nutritionalRequirement
chosen
Indicates that one entity has a need for certain nutrients or dietary conditions that must be met by another entity or resource.
-
C.
bloodMealRequirement
Indicates that an organism requires a blood meal, typically for development, reproduction, or survival.
-
D.
feedingHabitat
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
E.
feedingSpecialization
Indicates a relationship where an entity is specialized or adapted to feed on a particular type or range of food resources.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f454a02ac88190ae0a2ac9071622eb |
completed | May 1, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:09 a.m.