Triple
T23818052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liana radar |
E589148
|
entity |
| Predicate | controlFunction |
P115681
|
FINISHED |
| Object | vectoring fighter aircraft to targets |
—
|
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: vectoring fighter aircraft to targets | Statement: [Liana radar, controlFunction, vectoring fighter aircraft to targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlFunction Context triple: [Liana radar, controlFunction, vectoring fighter aircraft to targets]
-
A.
controlsSystem
chosen
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
B.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
C.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
D.
controlParameter
Indicates that one entity functions as a parameter that governs, tunes, or constrains the behavior or operation of another entity.
-
E.
controlStand
Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7ac0c688190a627b9b42c7587d5 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:58 p.m.