Triple
T9026368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GameCube controller |
E216055
|
entity |
| Predicate | usedAtOfficialTournament |
P13690
|
FINISHED |
| Object | Super Smash Bros. Melee tournaments |
—
|
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: Super Smash Bros. Melee tournaments | Statement: [GameCube controller, usedAtOfficialTournament, Super Smash Bros. Melee tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAtOfficialTournament Context triple: [GameCube controller, usedAtOfficialTournament, Super Smash Bros. Melee tournaments]
-
A.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
-
B.
firstUsedInTournament
Indicates that an entity (such as a move, strategy, or item) was used for the first time in a specific tournament.
-
C.
scoredInTournament
Indicates that an entity achieved a score or points during a particular tournament.
-
D.
usedInTournamentTables
Indicates that something (such as a rule, format, or data structure) is employed within the context of tournament tables.
-
E.
usedInCompetition
chosen
Indicates that something is employed or utilized as part of a competition or contest.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7ce71c81908041814dc9ec1713 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.