Triple
T11607749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Games of the XIX Olympiad |
E275304
|
entity |
| Predicate | hasOfficialMascot |
P100577
|
FINISHED |
| Object | none (no official mascot was used) |
—
|
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: none (no official mascot was used) | Statement: [Games of the XIX Olympiad, hasOfficialMascot, none (no official mascot was used)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialMascot Context triple: [Games of the XIX Olympiad, hasOfficialMascot, none (no official mascot was used)]
-
A.
hasMascot
Indicates that an entity is represented or symbolized by a particular mascot.
-
B.
isMascot
Indicates that one entity serves as the mascot or symbolic representative for another entity, such as an organization, team, or event.
-
C.
hasCompanionMascot
Indicates that an entity is accompanied by or associated with a specific mascot serving as its companion.
-
D.
mascotName
Indicates the name assigned to a mascot that represents an entity.
-
E.
hasMascotFeature
Indicates that an entity possesses a specific characteristic, attribute, or element related to a mascot.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89551649c81908096ff392677442d |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.