Triple
T15970146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AESA |
E387296
|
entity |
| Predicate | beamSteeringMethod |
P81650
|
FINISHED |
| Object | electronic phase shifting |
—
|
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: electronic phase shifting | Statement: [AESA, beamSteeringMethod, electronic phase shifting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamSteeringMethod Context triple: [AESA, beamSteeringMethod, electronic phase shifting]
-
A.
aimingMethod
chosen
Indicates the technique or approach used to direct or aim an action, object, or effect toward a target.
-
B.
beamExtractionMethod
Indicates the method or technique used to extract or generate a beam from a source.
-
C.
attitudeControlMethod
Indicates the technique or mechanism used to control or adjust the orientation or pointing direction of an object (such as a vehicle or device).
-
D.
beamUse
Indicates the action of directing or emitting a beam (such as light, energy, or signal) from one entity toward a target or in a specific direction.
-
E.
hasSteering
Indicates that one entity is equipped with or possesses a steering mechanism that allows control of its direction.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.