Triple
T34347081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimrod AEW3 |
E881463
|
entity |
| Predicate | radarTypeIntended |
P6751
|
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: [Nimrod AEW3, radarTypeIntended, pulse-Doppler radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarTypeIntended Context triple: [Nimrod AEW3, radarTypeIntended, pulse-Doppler radar]
-
A.
radarType
chosen
Indicates the specific category or classification of radar associated with an entity.
-
B.
radarFunction
Indicates that one entity serves as the functional role, purpose, or operational capability of a radar system in relation to another entity.
-
C.
radarEquipped
Indicates that an entity is equipped with or has access to radar detection equipment or radar-based sensing capability.
-
D.
radarInterface
Indicates that one entity serves as or provides a radar-based interface or interaction layer for another entity.
-
E.
radarConfiguration
Indicates a relationship where a radar system is associated with or defined by a specific configuration or setup of its operational parameters.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.