Triple
T15877982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Koopa |
E384997
|
entity |
| Predicate | hasForm |
P169
|
FINISHED |
| Object | Fury Bowser |
E74801
|
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: Fury Bowser | Statement: [King Koopa, hasForm, Fury Bowser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fury Bowser Context triple: [King Koopa, hasForm, Fury Bowser]
-
A.
Bowser
chosen
Bowser is the iconic fire-breathing, turtle-like villain from Nintendo’s Super Mario series, known as Mario’s arch-nemesis and the king of the Koopas.
-
B.
Bowser
Bowser is a small unincorporated coastal community on central Vancouver Island in British Columbia, Canada.
-
C.
Bowser Jr.
Bowser Jr. is a recurring antagonist in the Super Mario series, known as Bowser’s mischievous son who frequently schemes against Mario and his allies.
-
D.
Roy Koopa
Roy Koopa is one of the Koopalings in the Super Mario series, known for his bulky build, sunglasses, and role as a mid-level boss serving Bowser.
-
E.
Ludwig von Koopa
Ludwig von Koopa is one of the Koopalings in the Super Mario series, known for his wild blue hair, classical music-inspired name, and role as a recurring boss character.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e155fec9d4819081efea504e1e3952 |
completed | April 16, 2026, 9:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb7f3c9481908bdde67998263c5e |
completed | May 10, 2026, 2:20 a.m. |
Created at: April 10, 2026, 4:51 a.m.