Triple
T35363633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Büryan kebab |
E1021565
|
entity |
| Predicate | usesCookingTime |
P50957
|
FINISHED |
| Object | long |
—
|
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: long | Statement: [Büryan kebab, usesCookingTime, long]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCookingTime Context triple: [Büryan kebab, usesCookingTime, long]
-
A.
typicalCookingTime
chosen
Indicates the usual duration required to cook something under standard or commonly accepted conditions.
-
B.
usesCookingMethod
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
-
C.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
-
D.
preparationTimeContribution
Indicates how much a given factor, step, or participant adds to the total time required for preparation.
-
E.
typicalServingTime
Indicates the usual or standard time at which an event, service, or item is typically provided or made available.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 3, 2026, 4:03 p.m.