Triple
T615539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chain Home Low |
E12195
|
entity |
| Predicate | deploymentType |
P17151
|
FINISHED |
| Object | fixed radar station network |
—
|
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: fixed radar station network | Statement: [Chain Home Low, deploymentType, fixed radar station network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentType Context triple: [Chain Home Low, deploymentType, fixed radar station network]
-
A.
deploymentModel
Indicates the type or manner in which a system, service, or resource is deployed or made available (e.g., on-premises, cloud, hybrid).
-
B.
typicalDeployment
Indicates that one entity represents the standard or most commonly used deployment configuration or pattern for the other entity.
-
C.
deployedTo
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
-
D.
hasDeployment
Indicates that an entity is associated with or utilizes a specific deployment instance (e.g., of software, a model, or a system) in an operational context.
-
E.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.