Triple
T6097651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bane |
E135916
|
entity |
| Predicate | fightsStyle |
P35675
|
FINISHED |
| Object | brutal and efficient close-quarters combat |
—
|
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: brutal and efficient close-quarters combat | Statement: [Bane, fightsStyle, brutal and efficient close-quarters combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightsStyle Context triple: [Bane, fightsStyle, brutal and efficient close-quarters combat]
-
A.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
B.
martialArt
Indicates that one entity practices, performs, or is associated with a specific martial art style or discipline in relation to another entity.
-
C.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
-
D.
hasFightingStance
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
E.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a987ce081908cbe22940f31ee2f |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.