Triple
T9387693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S1850M long-range radar |
E225944
|
entity |
| Predicate | antennaRotation |
P88653
|
FINISHED |
| Object | mechanically rotating |
—
|
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: mechanically rotating | Statement: [S1850M long-range radar, antennaRotation, mechanically rotating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antennaRotation Context triple: [S1850M long-range radar, antennaRotation, mechanically rotating]
-
A.
antennaType
Indicates the specific kind or category of antenna associated with an entity or connection.
-
B.
broadcastAntenna
Indicates that an entity functions as a broadcast antenna used to transmit signals over a distance.
-
C.
notableAntenna
Indicates that an entity possesses an antenna that is particularly significant, prominent, or noteworthy in some relevant context.
-
D.
hasExternalAntenna
Indicates that an entity is equipped with or connected to an antenna located outside its main body or enclosure.
-
E.
antennaNickname
Indicates that an antenna has an associated informal or alternative name used to refer to it.
- F. None of above. chosen
Provenance (4 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d562a48190875d9fe3aae25a2b |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:45 p.m.