Triple
T25369015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-15 Gauntlet |
E632881
|
entity |
| Predicate | hasRadarFunction |
P158808
|
FINISHED |
| Object | target acquisition |
—
|
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: target acquisition | Statement: [SA-15 Gauntlet, hasRadarFunction, target acquisition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadarFunction Context triple: [SA-15 Gauntlet, hasRadarFunction, target acquisition]
-
A.
hasRadarControlRole
Indicates that an entity holds a role or responsibility related to managing or controlling radar operations.
-
B.
hasRadarServices
Indicates that one entity provides or is equipped with radar-based services or capabilities for another entity or context.
-
C.
radarEquipped
Indicates that an entity is equipped with or has access to radar detection equipment or radar-based sensing capability.
-
D.
radarFunction
chosen
Indicates that one entity serves as the functional role, purpose, or operational capability of a radar system in relation to another entity.
-
E.
radarType
Indicates the specific category or classification of radar associated with 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:38 p.m.