Triple
T21416251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papa Johns |
E528302
|
entity |
| Predicate | hasNotableMenuFeature |
P642
|
FINISHED |
| Object | garlic dipping sauce |
—
|
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: garlic dipping sauce | Statement: [Papa Johns, hasNotableMenuFeature, garlic dipping sauce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMenuFeature Context triple: [Papa Johns, hasNotableMenuFeature, garlic dipping sauce]
-
A.
hasNotableFeature
chosen
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
B.
hasMenuItem
Indicates that one entity (typically a menu or menu section) includes or offers another entity as one of its menu items.
-
C.
hasMenuBoard
Indicates that one entity provides or is equipped with a menu board associated with another entity.
-
D.
hasNotableItem
Indicates that an entity possesses, contains, or is associated with an item considered notable or significant in some context.
-
E.
hasNotableNative
Indicates that an entity is known for having a notable person, species, or element that originates from or is native to it.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b205d17c8190b9b6b5708658f9be |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:46 p.m.