Triple
T34124726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaslon phased-array radar |
E875241
|
entity |
| Predicate | radarMode |
P70235
|
FINISHED |
| Object | search |
—
|
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: search | Statement: [Zaslon phased-array radar, radarMode, search]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarMode Context triple: [Zaslon phased-array radar, radarMode, search]
-
A.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
B.
radarFunction
Indicates that one entity serves as the functional role, purpose, or operational capability of a radar system in relation to another entity.
-
C.
radarConfiguration
chosen
Indicates a relationship where a radar system is associated with or defined by a specific configuration or setup of its operational parameters.
-
D.
radarModel
Indicates that one entity is a radar system and the other is the specific model or type designation of that radar.
-
E.
radarInterface
Indicates that one entity serves as or provides a radar-based interface or interaction layer for another 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.