Triple
T3163434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | aloo paratha |
E66153
|
entity |
| Predicate | servedHotOrCold |
P14779
|
FINISHED |
| Object | hot |
—
|
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: hot | Statement: [aloo paratha, servedHotOrCold, hot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedHotOrCold Context triple: [aloo paratha, servedHotOrCold, hot]
-
A.
servingStyle
chosen
Indicates how something (typically food or drink) is presented or offered for consumption or use.
-
B.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
C.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
-
D.
servesMostly
Indicates that one entity primarily functions to serve, support, or cater to another entity, more than to any other.
-
E.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada61a4b8481908897a8d39d94c2f4 |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.