Triple
T4151405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Forest ham |
E89913
|
entity |
| Predicate | curingIngredient |
P12771
|
FINISHED |
| Object | salt |
—
|
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: salt | Statement: [Black Forest ham, curingIngredient, salt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curingIngredient Context triple: [Black Forest ham, curingIngredient, salt]
-
A.
usesIngredient
chosen
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
-
B.
ingredientType
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
C.
fieldTincture
Indicates the heraldic tincture (color, metal, or fur) applied to the main background field of a coat of arms.
-
D.
traditionallyBelievedToContain
Indicates that something is customarily or historically thought to include or hold something else, regardless of whether this belief is factually accurate.
-
E.
supporterTincture
Indicates that a heraldic supporter (a figure holding or standing beside the shield) bears a specified tincture (color or pattern).
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.