Triple
T112551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chain Home |
E2278
|
entity |
| Predicate | coverageArea |
P82
|
FINISHED |
| Object | British east and south coasts |
—
|
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: British east and south coasts | Statement: [Chain Home, coverageArea, British east and south coasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverageArea Context triple: [Chain Home, coverageArea, British east and south coasts]
-
A.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
B.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
C.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
D.
area
Indicates that one entity has a measured two-dimensional extent or surface size quantified by another entity.
-
E.
hasCatchmentArea
Indicates that a geographic or administrative unit serves as the area from which an entity (such as a facility or service) draws its users, resources, or influence.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.