Triple
T16546803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M38 carbine |
E401963
|
entity |
| Predicate | isMilitaryStandardIssue |
P83177
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [M38 carbine, isMilitaryStandardIssue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitaryStandardIssue Context triple: [M38 carbine, isMilitaryStandardIssue, true]
-
A.
isMilitaryOnly
Indicates that something is restricted exclusively to military use or participation, excluding civilians or non-military entities.
-
B.
militaryStandard
chosen
Indicates that something conforms to, is defined by, or is governed by an official military standard or specification.
-
C.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
D.
isMilitaryAssetOf
Indicates that something functions as a military resource, equipment, or facility that belongs to, is controlled by, or is used by a particular entity.
-
E.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
- 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.