Triple
T27131714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egg McMuffin |
E681577
|
entity |
| Predicate | isIconicItemOf |
P43625
|
FINISHED |
| Object | McDonald’s breakfast |
—
|
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: McDonald’s breakfast | Statement: [Egg McMuffin, isIconicItemOf, McDonald’s breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIconicItemOf Context triple: [Egg McMuffin, isIconicItemOf, McDonald’s breakfast]
-
A.
isIconicIn
chosen
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
-
B.
hasIconicStatus
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or context.
-
C.
hasIconicArtifact
Indicates that an entity possesses or is associated with a distinctive, emblematic artifact that represents its identity, history, or significance.
-
D.
hasIconicModel
Indicates that something is associated with or represented by a particularly famous or emblematic model.
-
E.
isIconicAddressOf
Indicates that one entity is a widely recognized, emblematic, or culturally significant address associated with the other entity.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6247832a48190b820e8c0c22ff5db |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:04 a.m.