Triple
T28575372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burger King |
E723224
|
entity |
| Predicate | signatureMenuItem |
P166227
|
FINISHED |
| Object | Whopper |
—
|
NE NERFINISHED |
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: Whopper | Statement: [Burger King, signatureMenuItem, Whopper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureMenuItem Context triple: [Burger King, signatureMenuItem, Whopper]
-
A.
signatureItem
Indicates that an entity is a component or element that forms part of another entity’s signature (such as a defining list, pattern, or parameter set).
-
B.
signatureCondiment
Indicates that something is the distinctive or characteristic condiment typically associated with a particular entity (such as a person, dish, or restaurant).
-
C.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
-
D.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
E.
signatureToppingStyle
Indicates the distinctive or characteristic way toppings are arranged or combined for a particular item.
- F. None of above. chosen
Provenance (4 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 4:12 a.m.