Triple
T855740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtic Sea |
E18487
|
entity |
| Predicate | easternBoundary |
P19400
|
FINISHED |
| Object | southwestern approaches to the English Channel |
—
|
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: southwestern approaches to the English Channel | Statement: [Celtic Sea, easternBoundary, southwestern approaches to the English Channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternBoundary Context triple: [Celtic Sea, easternBoundary, southwestern approaches to the English Channel]
-
A.
boundedToEastBy
chosen
Indicates that one entity’s eastern boundary is defined or limited by the presence or extent of another entity.
-
B.
westernBoundaryReference
Indicates the reference feature or limit that defines the western boundary of an entity or area.
-
C.
boundedToWestBy
Indicates that one entity’s western boundary is defined or delimited by another entity.
-
D.
southernBoundaryReference
Indicates that one entity is used as the reference or defining limit for the southern boundary of another entity.
-
E.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3c172481908ed164ee1579ec28 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.