Triple
T32703436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloodhound missile (later marks) |
E836204
|
entity |
| Predicate | radarAssociated |
P132889
|
FINISHED |
| Object | Ferranti Type 86 radar |
—
|
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: Ferranti Type 86 radar | Statement: [Bloodhound missile (later marks), radarAssociated, Ferranti Type 86 radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarAssociated Context triple: [Bloodhound missile (later marks), radarAssociated, Ferranti Type 86 radar]
-
A.
associatedRadar
chosen
Indicates that one entity is linked or connected to a specific radar system or radar-related resource.
-
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.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
D.
radarEquipped
Indicates that an entity is equipped with or has access to radar detection equipment or radar-based sensing capability.
-
E.
radarConfirmation
Indicates that an observed object, event, or target has been positively detected or verified using radar.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c84f0d188190ad72ab3317ebd9d3 |
completed | May 3, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:10 a.m.