Triple
T1680146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culture of Ukrainian borscht cooking |
E36319
|
entity |
| Predicate | involvesIngredient |
P12771
|
FINISHED |
| Object | beetroot |
—
|
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: beetroot | Statement: [Culture of Ukrainian borscht cooking, involvesIngredient, beetroot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesIngredient Context triple: [Culture of Ukrainian borscht cooking, involvesIngredient, beetroot]
-
A.
usesIngredient
chosen
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
-
B.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
C.
coFormulatedWith
Indicates that one entity is formulated together with another as part of the same combined product or composition.
-
D.
culinaryUse
Indicates that one entity is used in the preparation, flavoring, or serving of food or drink for another entity.
-
E.
formulatedIn
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.