Triple
T21439301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coburg bratwurst |
E528894
|
entity |
| Predicate | spiceProfile |
P44787
|
FINISHED |
| Object | mildlySeasoned |
—
|
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: mildlySeasoned | Statement: [Coburg bratwurst, spiceProfile, mildlySeasoned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiceProfile Context triple: [Coburg bratwurst, spiceProfile, mildlySeasoned]
-
A.
hasSpice
chosen
Indicates that one entity contains, includes, or is characterized by a particular spice or set of spices.
-
B.
roastProfile
Indicates the specific roasting characteristics or level applied to an item (typically coffee), defining how it was roasted.
-
C.
intendedFlavorProfile
Indicates the flavor characteristics that something is designed or planned to have, rather than what it actually tastes like.
-
D.
participantProfile
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
-
E.
profileType
Indicates the specific category or role classification assigned to a profile within a system.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b6feb2e48190ba5649f16a8bbbda |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6:04 p.m.