Triple
T19516290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OK K.O.! Let's Be Heroes |
E488285
|
entity |
| Predicate | mainCharacter |
P1183
|
FINISHED |
| Object | K.O. |
—
|
NE NERFINISHED |
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: K.O. | Statement: [OK K.O.! Let's Be Heroes, mainCharacter, K.O.]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: K.O. Context triple: [OK K.O.! Let's Be Heroes, mainCharacter, K.O.]
-
A.
K.O.
chosen
K.O. is the enthusiastic young aspiring hero and main character of the animated series "OK K.O.! Let's Be Heroes," known for his boundless optimism and determination to become the world’s greatest hero.
-
B.
K-Os
K-Os is a Canadian rapper, singer, songwriter, and producer known for his genre-blending style that fuses hip hop with rock, reggae, and alternative music.
-
C.
Ko
Ko is a Japanese given-name element commonly used in female names, often carrying meanings like “child” depending on the kanji used.
-
D.
Koo
Koo is a Korean family name associated with several prominent business and cultural figures in South Korea.
-
E.
K.O.P
K.O.P is a track featured on the hip-hop album "Purple Haze 2" by Cam'ron.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359ca7648190804c4d655170fda3 |
completed | April 20, 2026, 2:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.