Triple
T615523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chain Home Low |
E12195
|
entity |
| Predicate | designedToDetect |
P9494
|
FINISHED |
| Object | low-flying aircraft |
—
|
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: low-flying aircraft | Statement: [Chain Home Low, designedToDetect, low-flying aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToDetect Context triple: [Chain Home Low, designedToDetect, low-flying aircraft]
-
A.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
B.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
D.
helpsIdentify
Indicates a relationship where one entity serves to distinguish, recognize, or determine the identity or characteristics of another entity.
-
E.
radarType
Indicates the specific category or classification of radar associated with an 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e0b438881909ad515adf7a4eb79 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.