Triple
T16556746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talke |
E402225
|
entity |
| Predicate | distanceToKidsgrove |
P124044
|
FINISHED |
| Object | approximately 2 miles |
—
|
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 2 miles | Statement: [Talke, distanceToKidsgrove, approximately 2 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKidsgrove Context triple: [Talke, distanceToKidsgrove, approximately 2 miles]
-
A.
distanceToKidderminster
Indicates the measured or specified distance between a given entity and the location of Kidderminster.
-
B.
distanceToLanark
Indicates the spatial distance between a given entity or location and the place named Lanark.
-
C.
distanceToBathgate
Indicates the spatial distance between a given entity and the location Bathgate.
-
D.
distanceToKendal
Indicates the spatial distance between a given entity and the location named Kendal.
-
E.
distanceFromMoree
Indicates the spatial distance measured from the reference location Moree to another place or 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fca6db8819098c4f3919bb052d8 |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.