Triple
T15797279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faxfleet |
E383013
|
entity |
| Predicate | distanceToKingstonUponHull |
P120054
|
FINISHED |
| Object | approximately 20 miles west |
—
|
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: approximately 20 miles west | Statement: [Faxfleet, distanceToKingstonUponHull, approximately 20 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKingstonUponHull Context triple: [Faxfleet, distanceToKingstonUponHull, approximately 20 miles west]
-
A.
distanceToHunstanton
Indicates the measured spatial distance between a given entity and the location Hunstanton.
-
B.
distanceToSouthampton
Indicates the measured distance between a given entity’s location and the location of Southampton.
-
C.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
D.
distanceToSunderland_km
Indicates the physical distance, measured in kilometers, between a given place and Sunderland.
-
E.
distanceToHuddersfield
Indicates the spatial distance between a given entity or location and the town of Huddersfield.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4def80481908f72733ce9133bc6 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e006b17f7881908b8c7a37f0af4581 |
completed | April 15, 2026, 9:44 p.m. |
Created at: April 10, 2026, 4:48 a.m.