Triple
T16285796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K3 light machine gun |
E395384
|
entity |
| Predicate | hasSelector |
P122530
|
FINISHED |
| Object | full-automatic fire |
—
|
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: full-automatic fire | Statement: [K3 light machine gun, hasSelector, full-automatic fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSelector Context triple: [K3 light machine gun, hasSelector, full-automatic fire]
-
A.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
B.
hasNotableSelector
Indicates that an entity is associated with a particularly important or distinguished selector used to identify or access it.
-
C.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
D.
hasClassOptions
Indicates that an entity is associated with one or more selectable class options or classifications.
-
E.
hasSelectionBody
Indicates that an entity includes or is associated with a specific selection body, i.e., the defined content or portion that has been selected.
- F. None of above. chosen
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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24914bda08190a5d6315414ee3f76 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.