Triple
T28232712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipal Borough of Surbiton |
E711795
|
entity |
| Predicate | startPointAsUrbanDistrict |
P194172
|
FINISHED |
| Object | 1894 |
—
|
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: 1894 | Statement: [Municipal Borough of Surbiton, startPointAsUrbanDistrict, 1894]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPointAsUrbanDistrict Context triple: [Municipal Borough of Surbiton, startPointAsUrbanDistrict, 1894]
-
A.
hasUrbanDistrictNumber
Indicates that an entity is assigned a specific identifying number corresponding to its urban district.
-
B.
formsUrbanAreaWith
Indicates that two or more settlements are geographically and functionally connected so that together they constitute a single continuous urban area.
-
C.
endPointDistrict
Indicates the district in which a path, route, or connection terminates.
-
D.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
E.
isUrbanSectionOf
Indicates that one area or segment is the part of a larger entity that lies within an urban or city environment.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: April 27, 2026, 10:52 p.m.