Triple
T22712377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breda-SAFAT machine gun |
E561634
|
entity |
| Predicate | synchronizationCapability |
P127626
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Breda-SAFAT machine gun, synchronizationCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: synchronizationCapability Context triple: [Breda-SAFAT machine gun, synchronizationCapability, yes]
-
A.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
-
B.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
C.
bitSynchronizationSupport
chosen
Indicates whether a system, device, or protocol provides mechanisms to align and maintain timing at the bit level between communicating entities.
-
D.
demonstratedCapability
Indicates that an entity has shown, through evidence or performance, the ability to carry out a specific action or function.
-
E.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790998fc8190962e21a28dd08d29 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:18 p.m.