Triple
T4053225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islington South and Finsbury |
E84632
|
entity |
| Predicate | distanceFromCharingCrossApprox |
P35331
|
FINISHED |
| Object | about 2–3 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 2–3 miles north | Statement: [Islington South and Finsbury, distanceFromCharingCrossApprox, about 2–3 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCharingCrossApprox Context triple: [Islington South and Finsbury, distanceFromCharingCrossApprox, about 2–3 miles north]
-
A.
distanceToCharingCross
chosen
Indicates the spatial distance between a given location and Charing Cross.
-
B.
distanceFromBengaluru
Indicates the measured spatial distance between a given entity’s location and the city of Bengaluru.
-
C.
distanceToDelhiApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Delhi.
-
D.
distanceFromChennai
Indicates the spatial distance between a given entity or location and the city of Chennai.
-
E.
distanceFromChandigarh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Chandigarh.
- F. None of above.
Provenance (3 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.