Triple
T30982148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skelmersdale |
E789406
|
entity |
| Predicate | overspillFor |
P179054
|
FINISHED |
| Object | Liverpool |
—
|
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: Liverpool | Statement: [Skelmersdale, overspillFor, Liverpool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overspillFor Context triple: [Skelmersdale, overspillFor, Liverpool]
-
A.
overhangs
Indicates that one entity extends out beyond and above another, typically projecting past its edge or boundary.
-
B.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
C.
overlooks
Indicates that one entity has a view toward or looks out over another entity, typically from a higher or adjacent position.
-
D.
oversLimit
Indicates that an entity exceeds a specified limit, threshold, or allowed maximum.
-
E.
blowsOver
Indicates that one entity is toppled or knocked down by the force or movement of another entity.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 29, 2026, 8:55 p.m.