Triple
T20045382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pichu |
E497543
|
entity |
| Predicate | smashRole |
P68592
|
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: [Pichu, smashRole, playable fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smashRole Context triple: [Pichu, smashRole, playable fighter]
-
A.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
B.
playRoleIn
chosen
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
C.
covertRole
Indicates that an entity holds or performs a hidden, secret, or undercover role in relation to another entity or context.
-
D.
spinOffRole
Indicates that one role or position has been derived or created as a secondary or offshoot role from another original role.
-
E.
onamasticRole
Indicates a relationship where an entity holds a specific role or function within the system of naming or onomastics (e.g., as a name-bearer, name-giver, or type of name).
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662eea09481908d1001165e9d719c |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.