Triple
T25050416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AOC Bresse chicken |
E627361
|
entity |
| Predicate | finishingMethod |
P157582
|
FINISHED |
| Object | fattening in épinette (small cage) before slaughter |
—
|
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: fattening in épinette (small cage) before slaughter | Statement: [AOC Bresse chicken, finishingMethod, fattening in épinette (small cage) before slaughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishingMethod Context triple: [AOC Bresse chicken, finishingMethod, fattening in épinette (small cage) before slaughter]
-
A.
finishingMethod
chosen
Indicates the technique or process used to complete or finalize an object, task, or work.
-
B.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
C.
finisher
Indicates that an entity completes, concludes, or brings to an end a process, event, or sequence, often as the final actor or decisive contributor.
-
D.
finishingArea
Indicates the location or area where an activity, process, or event comes to an end or is completed.
-
E.
finish
Indicates that an entity brings an action, process, or state to an end or completion.
- 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_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:09 a.m.