Triple
T27720476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | curanto |
E698938
|
entity |
| Predicate | curantoEnOllaDefinition |
P61222
|
FINISHED |
| Object | curanto prepared in a large pot |
—
|
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: curanto prepared in a large pot | Statement: [curanto, curantoEnOllaDefinition, curanto prepared in a large pot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curantoEnOllaDefinition Context triple: [curanto, curantoEnOllaDefinition, curanto prepared in a large pot]
-
A.
isUsuallyCookedIn
chosen
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
-
B.
eggDescription
Indicates that an entity provides a textual description or characterization of an egg.
-
C.
culinaryStatus
Indicates the current state or condition of something in relation to cooking or food preparation (e.g., raw, cooked, undercooked, burnt).
-
D.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
E.
cooksSimilarTo
Indicates that one entity prepares or cooks food in a way that is similar to how another entity does.
- 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_69f6363b50f08190a0d8e16d748388f5 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:06 p.m.