Triple
T15534657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosalina (Super Smash Bros. series) |
E370310
|
entity |
| Predicate | fighterNumber |
P119058
|
FINISHED |
| Object | 48 (Super Smash Bros. Ultimate) |
—
|
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: 48 (Super Smash Bros. Ultimate) | Statement: [Rosalina (Super Smash Bros. series), fighterNumber, 48 (Super Smash Bros. Ultimate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fighterNumber Context triple: [Rosalina (Super Smash Bros. series), fighterNumber, 48 (Super Smash Bros. Ultimate)]
-
A.
fighter1
Indicates that the subject is the first participant or primary combatant in a fight or competitive physical confrontation.
-
B.
fighter1TitleDefenceNumber
Indicates the number of times the first fighter has defended their title.
-
C.
fighterOnCard
Indicates that a particular fighter is scheduled to appear on a specific fight card or event lineup.
-
D.
fleetNumbers
Indicates that there is an association between an entity and one or more identifying numbers assigned to it as part of a fleet.
-
E.
fighter2
Indicates that the subject is the second participant (opponent) in a fighting or combat relationship or event.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:06 a.m.