Triple
T32341135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gullac |
E826316
|
entity |
| Predicate | consumptionPattern |
P112132
|
FINISHED |
| Object | especially consumed during Ramadan evenings |
—
|
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: especially consumed during Ramadan evenings | Statement: [Gullac, consumptionPattern, especially consumed during Ramadan evenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consumptionPattern Context triple: [Gullac, consumptionPattern, especially consumed during Ramadan evenings]
-
A.
consumptionMethod
Indicates the manner or process by which something is consumed, used up, or ingested.
-
B.
consumptionState
Indicates the current status or condition of how something is being used up, consumed, or depleted.
-
C.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
-
D.
eatingHabit
chosen
Indicates a characteristic pattern or regularity in how an entity consumes food, such as what, when, or how it typically eats.
-
E.
primaryConsumptionContext
Indicates the main situation, setting, or context in which something is typically used, consumed, or experienced.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be20cd6c8190b365c130d0a286e7 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:48 a.m.