Triple
T20191325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Olimar |
E492983
|
entity |
| Predicate | fightingStyleInSmash |
P131423
|
FINISHED |
| Object | uses Pikmin as weapons |
—
|
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: uses Pikmin as weapons | Statement: [Captain Olimar, fightingStyleInSmash, uses Pikmin as weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightingStyleInSmash Context triple: [Captain Olimar, fightingStyleInSmash, uses Pikmin as weapons]
-
A.
打撃スタイル
Indicates a relationship where an entity is characterized by or associated with a particular style or manner of striking or hitting.
-
B.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
C.
fightingPreference
chosen
Indicates a relationship where one entity has a favored way, style, or choice of engaging in fights or combat relative to others.
-
D.
SmashBrosSpecialMove
Indicates that one character performs a unique special move or attack on another character within the context of a Super Smash Bros. match.
-
E.
hasFighter
Indicates that an entity possesses, controls, or is associated with a fighter (such as a combatant, combat vehicle, or fighting unit).
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad593f88190a1e534fed38b3cd7 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.