Triple
T12171290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cus D'Amato |
E289971
|
entity |
| Predicate | fightingStyleDeveloped |
P35675
|
FINISHED |
| Object | peek-a-boo style |
—
|
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: peek-a-boo style | Statement: [Cus D'Amato, fightingStyleDeveloped, peek-a-boo style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightingStyleDeveloped Context triple: [Cus D'Amato, fightingStyleDeveloped, peek-a-boo style]
-
A.
martialArt
Indicates that one entity practices, performs, or is associated with a specific martial art style or discipline in relation to another entity.
-
B.
打撃スタイル
Indicates a relationship where an entity is characterized by or associated with a particular style or manner of striking or hitting.
-
C.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
D.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
E.
isGrapplingArt
Indicates that the subject is a martial art or combat style primarily focused on grappling techniques such as holds, locks, and throws.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.