Triple
T10017133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury South |
E199522
|
entity |
| Predicate | directionWithinBorough |
P82745
|
FINISHED |
| Object | southern part of Bury |
—
|
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: southern part of Bury | Statement: [Bury South, directionWithinBorough, southern part of Bury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionWithinBorough Context triple: [Bury South, directionWithinBorough, southern part of Bury]
-
A.
directionWithinCity
chosen
Indicates a directional relationship specifying where something is located or oriented within the boundaries of a particular city.
-
B.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
C.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
D.
locatedInBoroughCommunityDistrict
Indicates that something is situated within a specific borough community district.
-
E.
locatedInDirectionFromNYC
Indicates that one place is situated in a specified compass direction relative to New York City.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd4c17848190bf1a8017e755ba75 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.