Triple
T6803234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-16V Viper upgrade |
E156236
|
entity |
| Predicate | hasRadarType |
P6751
|
FINISHED |
| Object | active electronically scanned array radar |
—
|
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: active electronically scanned array radar | Statement: [F-16V Viper upgrade, hasRadarType, active electronically scanned array radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadarType Context triple: [F-16V Viper upgrade, hasRadarType, active electronically scanned array radar]
-
A.
radarType
chosen
Indicates the specific category or classification of radar associated with an entity.
-
B.
hasRadarServices
Indicates that one entity provides or is equipped with radar-based services or capabilities for another entity or context.
-
C.
radarEquipment
Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to another entity.
-
D.
radarConfiguration
Indicates a relationship where a radar system is associated with or defined by a specific configuration or setup of its operational parameters.
-
E.
hasRadiusType
Indicates that an entity has a radius characterized by a specific type 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e8d7888190a837620967a150e3 |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.