Triple
T13450396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swettenham, Cheshire, England |
E320592
|
entity |
| Predicate | distanceToJodrellBank |
P109991
|
FINISHED |
| Object | nearby |
—
|
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: nearby | Statement: [Swettenham, Cheshire, England, distanceToJodrellBank, nearby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToJodrellBank Context triple: [Swettenham, Cheshire, England, distanceToJodrellBank, nearby]
-
A.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
B.
distanceToBingham
Indicates the measured or calculated distance between a given entity and the location named Bingham.
-
C.
distanceFromReading
Indicates the measured spatial distance between a specified entity and the location of Reading.
-
D.
distanceFromGiantCauseway
Indicates the measured distance between an entity and the Giant's Causeway.
-
E.
approxDistanceToJos
Indicates that one entity is located at an approximate distance from the entity referred to as Jos.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef973b08190a3d7fe1c2a913cff |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:41 p.m.