Triple
T32690565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASAMS |
E835844
|
entity |
| Predicate | systemVariant |
P176064
|
FINISHED |
| Object | NASAMS 1 |
—
|
NE NERFINISHED |
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: NASAMS 1 | Statement: [NASAMS, systemVariant, NASAMS 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemVariant Context triple: [NASAMS, systemVariant, NASAMS 1]
-
A.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
B.
systemOperatesOn
Indicates that a system performs operations, actions, or processing directly on a specified target or resource.
-
C.
systemBrand
Indicates the brand or manufacturer associated with a particular system.
-
D.
systemCharacteristics
Indicates the defining properties, behaviors, and constraints that characterize how a system operates or is configured.
-
E.
operatorSystem
Indicates a relationship where one entity functions as the operating system that manages or controls another entity (such as a device, application, or system).
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:09 a.m.