Triple
T1359290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-16 Fighting Falcon |
E29060
|
entity |
| Predicate | avionicsFeature |
P7133
|
FINISHED |
| Object | pulse-Doppler 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: pulse-Doppler radar | Statement: [F-16 Fighting Falcon, avionicsFeature, pulse-Doppler radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avionicsFeature Context triple: [F-16 Fighting Falcon, avionicsFeature, pulse-Doppler radar]
-
A.
avionics
chosen
Indicates that an entity is related to the electronic systems used to control, monitor, or assist the operation of aircraft or spacecraft.
-
B.
aerodynamicsFeature
Indicates that one entity possesses or is characterized by a specific aerodynamic property, component, or design feature affecting airflow and motion through air.
-
C.
airborneComponent
Indicates that one entity is a component or part of another entity specifically when that other entity is in an airborne state.
-
D.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
E.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c290db288190910fcfa17e902663 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.