Triple
T8550224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idli |
E202426
|
entity |
| Predicate | batterPreparationStep |
P18062
|
FINISHED |
| Object | soaking grains and lentils |
—
|
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: soaking grains and lentils | Statement: [Idli, batterPreparationStep, soaking grains and lentils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batterPreparationStep Context triple: [Idli, batterPreparationStep, soaking grains and lentils]
-
A.
batter
Indicates that one entity physically strikes or beats another entity, typically with repeated or forceful blows.
-
B.
typicalPreparation
Indicates the usual or standard way in which something is prepared or made.
-
C.
BakerYield
Indicates the amount or output produced by a baker, typically in terms of quantity or volume of baked goods resulting from a given process or batch.
-
D.
bakingSurface
Indicates that one entity serves as the surface or platform on which another entity is baked.
-
E.
traditionalPreparation
chosen
Indicates that something is prepared or made using customary, long-established methods or techniques associated with a particular culture or practice.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe75589d8819096177ddbd3dafcb6 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.