Triple
T8334235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chuck E. Cheese |
E195146
|
entity |
| Predicate | hasMenuItemCategory |
P61811
|
FINISHED |
| Object | pizza |
—
|
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: pizza | Statement: [Chuck E. Cheese, hasMenuItemCategory, pizza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMenuItemCategory Context triple: [Chuck E. Cheese, hasMenuItemCategory, pizza]
-
A.
hasMenuItem
Indicates that one entity (typically a menu or menu section) includes or offers another entity as one of its menu items.
-
B.
menuCategory
chosen
Indicates the classification relationship that assigns an item to a specific section or category within a menu.
-
C.
hasCategoryGroup
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
-
D.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
-
E.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fbe61f481909cde8ab2c42f89fc |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:57 p.m.