Triple
T28899417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poison |
E732911
|
entity |
| Predicate | roleInStreetFighter |
P197764
|
FINISHED |
| Object | playable fighter |
—
|
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: playable fighter | Statement: [Poison, roleInStreetFighter, playable fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInStreetFighter Context triple: [Poison, roleInStreetFighter, playable fighter]
-
A.
roleInMortalKombat
Indicates that one entity has a specific role or function within the context of the Mortal Kombat franchise or universe.
-
B.
roleInCobraKai
Indicates that an entity has a specific role or position within the context of Cobra Kai.
-
C.
roleInUFC
Indicates the specific capacity or position an entity holds within the context of the Ultimate Fighting Championship (UFC), such as fighter, referee, coach, or official.
-
D.
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.
-
E.
roleInMonsterVerse
Indicates that an entity has a specific role or function within the MonsterVerse franchise or universe.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69feaa477f7c81909382b3aa77e7e11c |
completed | May 9, 2026, 3:30 a.m. |
Created at: April 28, 2026, 8:01 a.m.