Triple
T29247866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King |
E741484
|
entity |
| Predicate | roleInKOF |
P198384
|
FINISHED |
| Object | recurring playable character |
—
|
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: recurring playable character | Statement: [King, roleInKOF, recurring playable character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInKOF Context triple: [King, roleInKOF, recurring playable character]
-
A.
roleInStreetFighter
Indicates the specific function or character position an entity holds within the context of the Street Fighter franchise.
-
B.
roleInMortalKombat
Indicates that one entity has a specific role or function within the context of the Mortal Kombat franchise or universe.
-
C.
roleInArtOfFighting
Indicates that an entity has a specific role or involvement in the creation, performance, or representation of the work "Art of Fighting."
-
D.
roleInCobraKai
Indicates that an entity has a specific role or position within the context of Cobra Kai.
-
E.
smashBrosRole
Indicates that one entity has a specific role or function related to the Super Smash Bros. game or its competitive context in relation to another entity.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: April 28, 2026, 12:33 p.m.