Triple
T9541135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airborne Stand-Off Radar |
E230158
|
entity |
| Predicate | radarLocationOnAircraft |
P17750
|
FINISHED |
| Object | fuselage-mounted radar canoe |
—
|
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: fuselage-mounted radar canoe | Statement: [Airborne Stand-Off Radar, radarLocationOnAircraft, fuselage-mounted radar canoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarLocationOnAircraft Context triple: [Airborne Stand-Off Radar, radarLocationOnAircraft, fuselage-mounted radar canoe]
-
A.
radarLocation
Indicates the geographic position where a radar system is installed or operating.
-
B.
locationOnAircraft
chosen
Indicates that one entity is physically situated on or within an aircraft.
-
C.
radarEquipment
Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to another entity.
-
D.
survivingAircraftLocation
Indicates the location where an aircraft that has survived an incident or event is situated.
-
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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e695948190ab107fff38c57de7 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:01 p.m.