Triple
T4911525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuchela |
E110242
|
entity |
| Predicate | offeredToKrishna |
P30751
|
FINISHED |
| Object | flattened rice (poha/aval) |
—
|
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: flattened rice (poha/aval) | Statement: [Kuchela, offeredToKrishna, flattened rice (poha/aval)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredToKrishna Context triple: [Kuchela, offeredToKrishna, flattened rice (poha/aval)]
-
A.
roleInKrishnaLife
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
-
B.
worshipersOffer
chosen
Indicates that worshipers present or dedicate offerings to a deity, sacred figure, or religious object.
-
C.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
D.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
E.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9c32148190a940a3733ecd1898 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.