Triple
T24812065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-3 Goa |
E620816
|
entity |
| Predicate | radarAssociatedWith |
P132889
|
FINISHED |
| Object | SNR-125 Low Blow |
—
|
NE NERFINISHED |
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: SNR-125 Low Blow | Statement: [SA-3 Goa, radarAssociatedWith, SNR-125 Low Blow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarAssociatedWith Context triple: [SA-3 Goa, radarAssociatedWith, SNR-125 Low Blow]
-
A.
associatedRadar
chosen
Indicates that one entity is linked or connected to a specific radar system or radar-related resource.
-
B.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
C.
radarInterface
Indicates that one entity serves as or provides a radar-based interface or interaction layer for another entity.
-
D.
radarEquipped
Indicates that an entity is equipped with or has access to radar detection equipment or radar-based sensing capability.
-
E.
radarEquipment
Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.