Triple
T20047946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 15 |
E497611
|
entity |
| Predicate | radarInstrument |
P32605
|
FINISHED |
| Object | synthetic aperture 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: synthetic aperture radar | Statement: [Venera 15, radarInstrument, synthetic aperture radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarInstrument Context triple: [Venera 15, radarInstrument, synthetic aperture radar]
-
A.
radarEquipment
chosen
Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to another entity.
-
B.
radarInterface
Indicates that one entity serves as or provides a radar-based interface or interaction layer for another entity.
-
C.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
D.
radarModel
Indicates that one entity is a radar system and the other is the specific model or type designation of that radar.
-
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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632c085081908710cbc939ac9971 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.