Triple
T29089853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cody Travers |
E734823
|
entity |
| Predicate | fightingGameSeries |
P100028
|
FINISHED |
| Object | Street Fighter |
—
|
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: Street Fighter | Statement: [Cody Travers, fightingGameSeries, Street Fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightingGameSeries Context triple: [Cody Travers, fightingGameSeries, Street Fighter]
-
A.
notableFightSeries
Indicates that there is a recurring or thematically linked series of fights or battles associated with the subject.
-
B.
seriesGame
Indicates that a game is part of, or belongs to, a particular series or franchise.
-
C.
hasFighter
Indicates that an entity possesses, controls, or is associated with a fighter (such as a combatant, combat vehicle, or fighting unit).
-
D.
peakFighting
Indicates that an entity is engaging in combat or conflict at the highest or most intense level of its fighting capability.
-
E.
gameFranchise
chosen
Indicates that one entity is a video game franchise to which the other entity (such as a specific game, character, or related media) belongs or is associated.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 11:04 a.m.