Triple
T29049595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alentejo pork products |
E735229
|
entity |
| Predicate | usesFeedingSystem |
P15764
|
FINISHED |
| Object | montanheira (acorn finishing) |
—
|
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: montanheira (acorn finishing) | Statement: [Alentejo pork products, usesFeedingSystem, montanheira (acorn finishing)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFeedingSystem Context triple: [Alentejo pork products, usesFeedingSystem, montanheira (acorn finishing)]
-
A.
feederSystem
Indicates a system or mechanism that supplies or feeds resources, materials, or inputs into another process, component, or structure.
-
B.
feedingType
chosen
Indicates the manner or method by which one entity provides nourishment or food to another.
-
C.
includesFeedingType
Indicates that one entity encompasses or specifies a particular type or category of feeding associated with another entity.
-
D.
hasFillingSystem
Indicates that an entity is equipped with or uses a particular filling system or mechanism.
-
E.
hasFeederArea
Indicates that one entity serves as the source or contributing area that supplies resources, inputs, or influence to 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 10:07 a.m.