Triple
T32136064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asure |
E820765
|
entity |
| Predicate | isOftenPreparedOn |
P102145
|
FINISHED |
| Object | 10th day of Muharram |
—
|
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: 10th day of Muharram | Statement: [Asure, isOftenPreparedOn, 10th day of Muharram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenPreparedOn Context triple: [Asure, isOftenPreparedOn, 10th day of Muharram]
-
A.
isOftenPreparedTableside
Indicates that the dish or item is frequently assembled, cooked, or finished in front of guests at their table rather than entirely in the kitchen.
-
B.
commonlyPreparedFor
chosen
Indicates that something is typically made, organized, or arranged in anticipation of a particular event, purpose, or recipient.
-
C.
typeOfPreparation
Indicates the method or process by which something is prepared or made ready for use, consumption, or further action.
-
D.
isUsuallyCookedIn
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
-
E.
isOftenEaten
Indicates that the subject is frequently consumed as food by some agent or group.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 12:30 a.m.