Triple
T2509065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1968 Summer Olympics |
E52656
|
entity |
| Predicate | mascotStatus |
P40901
|
FINISHED |
| Object | held before official Olympic mascots were introduced |
—
|
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: held before official Olympic mascots were introduced | Statement: [1968 Summer Olympics, mascotStatus, held before official Olympic mascots were introduced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mascotStatus Context triple: [1968 Summer Olympics, mascotStatus, held before official Olympic mascots were introduced]
-
A.
isMascot
Indicates that one entity serves as the mascot or symbolic representative for another entity, such as an organization, team, or event.
-
B.
hasMascot
Indicates that an entity is represented or symbolized by a particular mascot.
-
C.
mascotTheme
Indicates that an entity serves as the representative mascot associated with a particular theme, concept, or style.
-
D.
coMascot
Indicates that two entities serve together as mascots for the same organization, event, or group.
-
E.
hasCompanionMascot
Indicates that an entity is accompanied by or associated with a specific mascot serving as its companion.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd65c9d508190957285a078698ed2 |
completed | March 7, 2026, 7:40 a.m. |
Created at: March 6, 2026, 9:46 p.m.