Triple
T31847164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Maria–style barbecue |
E812971
|
entity |
| Predicate | primaryCutOfMeat |
P10566
|
FINISHED |
| Object | tri-tip |
—
|
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: tri-tip | Statement: [Santa Maria–style barbecue, primaryCutOfMeat, tri-tip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCutOfMeat Context triple: [Santa Maria–style barbecue, primaryCutOfMeat, tri-tip]
-
A.
commonMeatCut
chosen
Indicates that two items are the same or equivalent cut of meat, or that an item belongs to a standard, commonly recognized meat cut category.
-
B.
meatType
Indicates the specific category or kind of meat associated with an entity.
-
C.
typicalMeat
Indicates that something is commonly or characteristically used or regarded as meat in a given context.
-
D.
meatContent
Indicates that one entity has a specified amount, proportion, or presence of meat contained within it.
-
E.
notableMeatProduct
Indicates that one entity is a meat-based product that is especially prominent, well-known, or significant in relation to the other 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:50 p.m.