Triple
T16353390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIT-RADWAR |
E397112
|
entity |
| Predicate | product |
P490
|
FINISHED |
| Object | NUR-31M radar |
E1211139
|
NE 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: NUR-31M radar | Statement: [PIT-RADWAR, product, NUR-31M radar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NUR-31M radar Context triple: [PIT-RADWAR, product, NUR-31M radar]
-
A.
NUR-31 radar
chosen
The NUR-31 radar is a Polish ground-based air-surveillance radar system developed by PIT-RADWAR for detecting and tracking aerial targets.
-
B.
NUR-21 radar
The NUR-21 radar is a Polish ground-based air-surveillance radar system developed by PIT-RADWAR for detecting and tracking aerial targets.
-
C.
NUR-41 radar
The NUR-41 radar is a Polish ground-based air-surveillance radar system developed by PIT-RADWAR for military airspace monitoring and target detection.
-
D.
NUR-22 radar
The NUR-22 radar is a Polish ground-based air-surveillance radar system developed by PIT-RADWAR for detecting and tracking aerial targets.
-
E.
NUR-12 radar family
The NUR-12 radar family is a series of Polish 3D air-surveillance and target-tracking radars designed for modern air defense systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2faccab748190b11e0808e422f2ea |
completed | April 18, 2026, 3:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006798cf488190a68cf7e57902924e |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:07 a.m.