Triple
T16415082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2 Black Panther |
E398662
|
entity |
| Predicate | autoloaderRateOfFire |
P17731
|
FINISHED |
| Object | up to 10 rounds per minute |
—
|
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: up to 10 rounds per minute | Statement: [K2 Black Panther, autoloaderRateOfFire, up to 10 rounds per minute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autoloaderRateOfFire Context triple: [K2 Black Panther, autoloaderRateOfFire, up to 10 rounds per minute]
-
A.
rateOfFire
chosen
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
B.
autoloaderCapacity
Indicates the maximum quantity or volume that an autoloader can hold or process at one time.
-
C.
fireModes
Indicates the different ways or settings in which a weapon or device can be fired or operated.
-
D.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
-
E.
fireballFrequency
Indicates how often fireball events occur or are produced within a given context or time period.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3287741008190856882b7f34024fc |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.