Triple
T12908981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pineapple Passionfruit Refresher |
E308800
|
entity |
| Predicate | menuSection |
P61811
|
FINISHED |
| Object | Cold drinks |
—
|
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: Cold drinks | Statement: [Pineapple Passionfruit Refresher, menuSection, Cold drinks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: menuSection Context triple: [Pineapple Passionfruit Refresher, menuSection, Cold drinks]
-
A.
menuCategory
chosen
Indicates the classification relationship that assigns an item to a specific section or category within a menu.
-
B.
menuItemType
Indicates the relationship between a menu item and the type or category it belongs to (e.g., appetizer, main course, dessert).
-
C.
menuPath
Indicates the hierarchical navigation route or sequence of menu items used to access a particular option or function within a menu system.
-
D.
homeSection
Indicates that something belongs to, is part of, or is designated as the primary/home section within a larger structure or collection.
-
E.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9719e584c81909be1ac1366effca0 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.