Triple
T33942213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M25 sniper weapon system |
E870193
|
entity |
| Predicate | originatesFromWeaponFamily |
P162933
|
FINISHED |
| Object | M14 rifle family |
E248916
|
NE 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: M14 rifle family | Statement: [M25 sniper weapon system, originatesFromWeaponFamily, M14 rifle family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromWeaponFamily Context triple: [M25 sniper weapon system, originatesFromWeaponFamily, M14 rifle family]
-
A.
weaponFamily
chosen
Indicates that two weapons belong to the same broader classification or type group based on shared characteristics or lineage.
-
B.
refersToWeaponPredecessor
Indicates that one weapon is identified as the predecessor or earlier version in the development or lineage of another weapon.
-
C.
isStartingWeaponFor
Indicates that a weapon is the initial or default weapon assigned to or used by an entity at the start of a game, scenario, or progression.
-
D.
refersToWeaponSuccessor
Indicates that one weapon is recognized as the successor or follow-up version to another weapon.
-
E.
formerWeapon
Indicates that an entity once functioned as a weapon but no longer serves in that role.
- F. None of above.
Provenance (4 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3692d068b081908b7a6f5cf176ec4d |
completed | June 20, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.