Triple
T24343736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northrop Grumman MESA radar |
E613583
|
entity |
| Predicate | antennaPlacement |
P83815
|
FINISHED |
| Object | mounted on top of aircraft fuselage |
—
|
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: mounted on top of aircraft fuselage | Statement: [Northrop Grumman MESA radar, antennaPlacement, mounted on top of aircraft fuselage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antennaPlacement Context triple: [Northrop Grumman MESA radar, antennaPlacement, mounted on top of aircraft fuselage]
-
A.
antennaType
Indicates the specific kind or category of antenna associated with an entity or connection.
-
B.
antennaRotation
Indicates the rotational movement or orientation change of an antenna relative to a reference frame or axis.
-
C.
broadcastAntenna
Indicates that an entity functions as a broadcast antenna used to transmit signals over a distance.
-
D.
notableAntenna
Indicates that an entity possesses an antenna that is particularly significant, prominent, or noteworthy in some relevant context.
-
E.
hasExternalAntenna
chosen
Indicates that an entity is equipped with or connected to an antenna located outside its main body or enclosure.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293270c908190872e0ec38f391fa5 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.