Triple
T34603734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Cup Willie (song) |
E888536
|
entity |
| Predicate | hasMascotCounterpart |
P160449
|
FINISHED |
| Object | World Cup Willie (mascot) |
E256348
|
NE 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: World Cup Willie (mascot) | Statement: [World Cup Willie (song), hasMascotCounterpart, World Cup Willie (mascot)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMascotCounterpart Context triple: [World Cup Willie (song), hasMascotCounterpart, World Cup Willie (mascot)]
-
A.
isMascotCounterpartOf
chosen
Indicates that one entity serves as the mascot equivalent or counterpart of another entity, typically representing the same thing in a mascot form.
-
B.
hasMascot
Indicates that an entity is represented or symbolized by a particular mascot.
-
C.
hasCompanionMascot
Indicates that an entity is accompanied by or associated with a specific mascot serving as its companion.
-
D.
hasSiblingMascot
Indicates that one mascot is a sibling (e.g., brother or sister) of another mascot.
-
E.
isMascot
Indicates that one entity serves as the mascot or symbolic representative for another entity, such as an organization, team, or event.
- F. None of above.
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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01b841f5508190832bba00cf795bad |
completed | May 11, 2026, 11:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bce661481909e3da11f22b954ef |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_6a01b59541fc8190a9b13a55327c4aa1 |
completed | May 11, 2026, 10:55 a.m. |
Created at: May 1, 2026, 2:03 a.m.