Triple
T31660306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hereford Street, Christchurch |
E807982
|
entity |
| Predicate | isCentralThoroughfare |
P45386
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hereford Street, Christchurch, isCentralThoroughfare, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralThoroughfare Context triple: [Hereford Street, Christchurch, isCentralThoroughfare, true]
-
A.
isCentralPoliticalThoroughfareOf
Indicates that a road or street serves as the main political route or corridor within a specified area, typically hosting key government or political institutions and activities.
-
B.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
C.
isInnerCityRoad
chosen
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
-
D.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
E.
isSideStreetOf
Indicates that one street is a smaller, less prominent road that connects to or branches off from another main street.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 10:57 p.m.