Triple
T4460219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscypek |
E98233
|
entity |
| Predicate | secondaryIngredient |
P28553
|
FINISHED |
| Object | cow’s milk |
—
|
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: cow’s milk | Statement: [Oscypek, secondaryIngredient, cow’s milk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryIngredient Context triple: [Oscypek, secondaryIngredient, cow’s milk]
-
A.
secondaryConstituent
chosen
Indicates that one entity functions as a secondary or subordinate component, element, or member within the structure or composition of another entity.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
D.
ingredientType
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
E.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35673337c8190b923159791ec27e3 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.