Triple
T17226003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Winter Paralympics |
E418114
|
entity |
| Predicate | paralympicMascot |
P18031
|
FINISHED |
| Object | Bandabi |
E533161
|
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: Bandabi | Statement: [2018 Winter Paralympics, paralympicMascot, Bandabi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bandabi Context triple: [2018 Winter Paralympics, paralympicMascot, Bandabi]
-
A.
Bandabi
chosen
Bandabi is the Asiatic black bear mascot of the PyeongChang 2018 Winter Paralympic Games, symbolizing courage and strong will.
-
B.
Bindabasini
Bindabasini is a town located within Nepal's Madhesh Province.
-
C.
Derabish
Derabish is a town and administrative block in the Kendrapara district of the Indian state of Odisha.
-
D.
Biddaddaba
Biddaddaba is a rural locality in Queensland, Australia, known for its scenic countryside and agricultural character within the Scenic Rim region.
-
E.
Nabitasan
Nabitasan is a barangay (village-level administrative division) of the municipality of Oton in the province of Iloilo, Philippines.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42de1674c81909ca9e87fa9153640 |
completed | April 19, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01675cc70881909cf39b2e229f5d1e |
completed | May 11, 2026, 5:21 a.m. |
Created at: April 10, 2026, 5:38 a.m.