Triple
T28354146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZB vz. 26 |
E718177
|
entity |
| Predicate | standardIssueRole |
P13409
|
FINISHED |
| Object | squad automatic weapon |
—
|
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: squad automatic weapon | Statement: [ZB vz. 26, standardIssueRole, squad automatic weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardIssueRole Context triple: [ZB vz. 26, standardIssueRole, squad automatic weapon]
-
A.
standardIssueFor
chosen
Indicates that something is the typical or officially designated item or version provided for use in a particular context, role, or organization.
-
B.
standardIssueFrom
Indicates that one entity is the official or default item provided or distributed by another entity as part of a standard set, kit, or issue.
-
C.
standardIssueUntil
Indicates the time or condition up to which something is considered standard issue or officially supplied.
-
D.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
E.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 12:48 a.m.