Triple
T32353402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian cuisine |
E826662
|
entity |
| Predicate | commonMealOccasion |
P53136
|
FINISHED |
| Object | Australia Day celebrations |
—
|
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: Australia Day celebrations | Statement: [Australian cuisine, commonMealOccasion, Australia Day celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMealOccasion Context triple: [Australian cuisine, commonMealOccasion, Australia Day celebrations]
-
A.
commonMealType
Indicates that two entities share the same general category or type of meal (e.g., breakfast, lunch, dinner).
-
B.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
C.
eatenOnOccasion
Indicates that one entity is consumed or eaten by another only at certain times or under specific circumstances, rather than regularly or habitually.
-
D.
typicallyEatenAt
chosen
Indicates that something is most commonly or customarily eaten during a particular time, event, or context.
-
E.
occasionType
Indicates the specific kind or category of occasion or event associated with the subject.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 1, 2026, 12:49 a.m.