Triple
T9542340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | piti |
E230187
|
entity |
| Predicate | requiresPreparationTime |
P24075
|
FINISHED |
| Object | several hours |
—
|
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: several hours | Statement: [piti, requiresPreparationTime, several hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPreparationTime Context triple: [piti, requiresPreparationTime, several hours]
-
A.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
-
B.
preparationRequirement
Indicates that one entity must be prepared, configured, or made ready as a necessary condition before another entity, action, or process can occur or be valid.
-
C.
preparationPeriod
chosen
Indicates the time span allocated before an event or action during which necessary preparations are made.
-
D.
typicalCookingTime
Indicates the usual duration required to cook something under standard or commonly accepted conditions.
-
E.
preparationInvolved
Indicates that a particular preparation, process, or setup is involved in enabling or carrying out an action, event, or relationship.
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e82bb08190aed3ed0627923d22 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:01 p.m.