Triple
T28232713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipal Borough of Surbiton |
E711795
|
entity |
| Predicate | startPointAsMunicipalBorough |
P194243
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [Municipal Borough of Surbiton, startPointAsMunicipalBorough, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPointAsMunicipalBorough Context triple: [Municipal Borough of Surbiton, startPointAsMunicipalBorough, 1936]
-
A.
startPointAsUrbanDistrict
Indicates that the starting point of something (e.g., a route, event, or process) is located within an urban district.
-
B.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
C.
hasMunicipalBorough
Indicates that an administrative unit possesses or contains a specific municipal borough as part of its jurisdiction or structure.
-
D.
boroughServed
Indicates that a given entity (such as a facility, service, or route) serves or provides coverage to a specific borough.
-
E.
governingBoroughSeat
Indicates that one entity serves as the administrative seat or central governing location for a particular borough.
- 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_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: April 27, 2026, 10:52 p.m.