Triple
T16467977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King K. Rool |
E399982
|
entity |
| Predicate | SmashBrosFighterType |
P60013
|
FINISHED |
| Object | heavyweight |
—
|
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: heavyweight | Statement: [King K. Rool, SmashBrosFighterType, heavyweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SmashBrosFighterType Context triple: [King K. Rool, SmashBrosFighterType, heavyweight]
-
A.
hasFighter
Indicates that an entity possesses, controls, or is associated with a fighter (such as a combatant, combat vehicle, or fighting unit).
-
B.
typeOfCharacter
chosen
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
C.
primaryFighterModel
Indicates that one entity is the main or standard fighter aircraft model associated with another entity (such as a country, air force, or military unit).
-
D.
amiiboSeries
Indicates the specific amiibo product line or series to which an amiibo-related entity belongs.
-
E.
featuredFighter
Indicates that a particular fighter is highlighted or prominently showcased in a given context or event.
- F. None of above.
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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dce342081909cad56dc92de13a2 |
completed | April 18, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.