Triple
T27720453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | curanto |
E698938
|
entity |
| Predicate | usesCookingSurface |
P160060
|
FINISHED |
| Object | hot stones |
—
|
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 stones | Statement: [curanto, usesCookingSurface, hot stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCookingSurface Context triple: [curanto, usesCookingSurface, hot stones]
-
A.
cookingSurface
chosen
Indicates that one entity serves as the surface or area on which another entity is used for cooking.
-
B.
bakingSurface
Indicates that one entity serves as the surface or platform on which another entity is baked.
-
C.
hasGasCooker
Indicates that an entity is equipped with or contains a gas-powered cooking appliance.
-
D.
cookingAppliance
Indicates that one entity is an appliance used by another entity for cooking food.
-
E.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 3:06 p.m.