Triple
T1843279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Striker Eureka |
E41226
|
entity |
| Predicate | combatStyle |
P22495
|
FINISHED |
| Object | 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: close-quarters combat | Statement: [Striker Eureka, combatStyle, close-quarters combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatStyle Context triple: [Striker Eureka, combatStyle, close-quarters combat]
-
A.
hasFightingStance
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
B.
weaponDiscipline
chosen
Indicates that an entity practices, adheres to, or is governed by a particular system, style, or code of weapon use or combat training.
-
C.
martialArt
Indicates that one entity practices, performs, or is associated with a specific martial art style or discipline in relation to another entity.
-
D.
shootingStyle
Indicates the characteristic manner or technique with which an entity performs a shooting action (e.g., in sports or photography).
-
E.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.