Triple
T26618426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form VII |
E668128
|
entity |
| Predicate | combatStyleType |
P35675
|
FINISHED |
| Object | aggressive |
—
|
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: aggressive | Statement: [Form VII, combatStyleType, aggressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatStyleType Context triple: [Form VII, combatStyleType, aggressive]
-
A.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
B.
boxingStyleCharacteristic
Indicates that a particular boxing style possesses or is defined by a specific characteristic or attribute.
-
C.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
D.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
E.
打撃スタイル
Indicates a relationship where an entity is characterized by or associated with a particular style or manner of striking or hitting.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615af6b488190819cd865b9b7527e |
completed | May 2, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:19 a.m.