Triple
T5276506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voodoo Doughnut |
E119382
|
entity |
| Predicate | hasMenuItemFeature |
P182
|
FINISHED |
| Object | cereal-topped doughnuts |
—
|
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: cereal-topped doughnuts | Statement: [Voodoo Doughnut, hasMenuItemFeature, cereal-topped doughnuts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMenuItemFeature Context triple: [Voodoo Doughnut, hasMenuItemFeature, cereal-topped doughnuts]
-
A.
hasMenuItem
Indicates that one entity (typically a menu or menu section) includes or offers another entity as one of its menu items.
-
B.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:51 p.m.