Triple
T36953256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancer assault rifle |
E914127
|
entity |
| Predicate | closeQuartersCapability |
P183574
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Lancer assault rifle, closeQuartersCapability, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closeQuartersCapability Context triple: [Lancer assault rifle, closeQuartersCapability, high]
-
A.
combatRangeSpecialty
chosen
Indicates a relationship where an entity is specialized or particularly effective in combat at a specific range (e.g., close, mid, or long distance).
-
B.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
-
C.
defensiveCapability
Indicates the ability or capacity of an entity to protect itself or others against threats, attacks, or harm.
-
D.
hasPerspectiveOnCombat
Indicates a relationship where an entity holds a particular viewpoint, attitude, or stance regarding combat or warfare.
-
E.
hasTacticalMobility
Indicates the capability of an entity to move or be repositioned quickly and effectively within a tactical or operational 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:13 p.m.