Triple
T24726446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedge Row |
E618165
|
entity |
| Predicate | menuFocus |
P86548
|
FINISHED |
| Object | farm-to-table style dishes |
—
|
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: farm-to-table style dishes | Statement: [Hedge Row, menuFocus, farm-to-table style dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: menuFocus Context triple: [Hedge Row, menuFocus, farm-to-table style dishes]
-
A.
menuPath
Indicates the hierarchical navigation route or sequence of menu items used to access a particular option or function within a menu system.
-
B.
menuType
Indicates the classification or category of a menu (e.g., main menu, context menu, settings menu) associated with an interface or system.
-
C.
focusOf
chosen
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
D.
importFocus
Indicates that attention, priority, or emphasis is being brought into or concentrated on a particular entity or aspect.
-
E.
menuItemType
Indicates the relationship between a menu item and the type or category it belongs to (e.g., appetizer, main course, dessert).
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:59 a.m.