Triple
T16546829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish M39 |
E401964
|
entity |
| Predicate | hasMuzzleVelocity |
P37993
|
FINISHED |
| Object | approximately 800–830 m/s |
—
|
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: approximately 800–830 m/s | Statement: [Finnish M39, hasMuzzleVelocity, approximately 800–830 m/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMuzzleVelocity Context triple: [Finnish M39, hasMuzzleVelocity, approximately 800–830 m/s]
-
A.
muzzleVelocity
chosen
Indicates the speed at which a projectile leaves the muzzle of a firearm or similar weapon at the moment it is fired.
-
B.
hasMuzzle
Indicates that one entity possesses or is equipped with a muzzle, typically as a restraining or protective device.
-
C.
typicalMuzzleEnergy
Indicates the usual or characteristic amount of muzzle energy associated with a given weapon or ammunition type.
-
D.
muzzleType
Indicates the specific style or configuration of a muzzle associated with an entity, such as a weapon or animal.
-
E.
hasDetonationVelocity
Indicates the specific speed at which a material’s detonation wave propagates through it during an explosive reaction.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbe3fb48190bad143b50dc73c7e |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.