Triple
T28865327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filey railway station |
E728980
|
entity |
| Predicate | hasDistanceFromHull |
P192369
|
FINISHED |
| Object | about 45 miles north |
—
|
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: about 45 miles north | Statement: [Filey railway station, hasDistanceFromHull, about 45 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceFromHull Context triple: [Filey railway station, hasDistanceFromHull, about 45 miles north]
-
A.
hasNearbyPoint
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
-
B.
hasBoundaryPoint
Indicates that one entity includes a point that lies on the boundary of another entity.
-
C.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
D.
hasDistanceElement
Indicates that one entity includes or is associated with a component that specifies a distance value or measurement.
-
E.
hasNearbyBoundary
Indicates that one entity’s boundary lies close to, but does not necessarily touch or coincide with, the boundary 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: April 28, 2026, 6:48 a.m.