Triple
T25413224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish Sea drainage basin |
E636759
|
entity |
| Predicate | includesCoastlineOf |
P105578
|
FINISHED |
| Object | England |
—
|
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: England | Statement: [Irish Sea drainage basin, includesCoastlineOf, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCoastlineOf Context triple: [Irish Sea drainage basin, includesCoastlineOf, England]
-
A.
includesCoastOf
chosen
Indicates that one geographic or administrative entity encompasses or contains the coastline of another entity.
-
B.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
C.
isPartOfCoastOf
Indicates that one entity forms a segment or component of the coastline belonging to another entity.
-
D.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
E.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 21, 2026, 1:55 p.m.