Triple
T13357152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morton Koopa Jr. |
E318721
|
entity |
| Predicate | battleStyle |
P50132
|
FINISHED |
| Object | ground pound attacks |
—
|
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: ground pound attacks | Statement: [Morton Koopa Jr., battleStyle, ground pound attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleStyle Context triple: [Morton Koopa Jr., battleStyle, ground pound attacks]
-
A.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
B.
battleSystem
Indicates a relationship where entities are engaged in or governed by a structured combat or conflict-resolution mechanism.
-
C.
tacticalStyle
chosen
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
D.
battleTarget
Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
-
E.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da62887e588190bd7241c720a112a2 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.