Triple
T35808179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boss |
E1035156
|
entity |
| Predicate | hasSignatureMoveType |
P108696
|
FINISHED |
| Object | crossface submission |
—
|
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: crossface submission | Statement: [The Boss, hasSignatureMoveType, crossface submission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureMoveType Context triple: [The Boss, hasSignatureMoveType, crossface submission]
-
A.
usesSignatureMove
chosen
Indicates that an entity performs or employs a distinctive, characteristic move or technique associated specifically with it.
-
B.
hasMoveType
Indicates that an action or move is associated with a specific type or category (such as elemental, functional, or classification-based).
-
C.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
D.
hasSignatureMatchType
Indicates that there is a correspondence between entities based on a specific type or pattern of signature used for matching.
-
E.
hasSignatureMechanic
Indicates that an entity (such as a game, character, or system) possesses a distinctive, defining mechanic or feature that is uniquely characteristic of it.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.