Triple
T25818486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirrin Bay |
E650330
|
entity |
| Predicate | locatedOnFictionalCoastOf |
P159629
|
FINISHED |
| Object | English Channel |
—
|
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: English Channel | Statement: [Kirrin Bay, locatedOnFictionalCoastOf, English Channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnFictionalCoastOf Context triple: [Kirrin Bay, locatedOnFictionalCoastOf, English Channel]
-
A.
locatedOnCoastAt
Indicates that one entity is situated on the coastline at the specific location represented by another entity.
-
B.
locatedInFictionalOcean
Indicates that something exists or is situated within a fictional or imaginary ocean setting.
-
C.
isFoundAlongCoastOf
chosen
Indicates that something occurs, exists, or is located adjacent to or near the coastline of a specified place.
-
D.
isCoastalSettlementOf
Indicates that a settlement is located on or near the coast within the territory of a specified geographic or administrative area.
-
E.
isPartOfCoastOf
Indicates that one entity forms a segment or component of the coastline belonging to another 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 22, 2026, 7:27 a.m.