Triple
T25459175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitcham and Morden |
E637995
|
entity |
| Predicate | governingBorough |
P37587
|
FINISHED |
| Object | Merton London Borough Council |
—
|
NE NERFINISHED |
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: Merton London Borough Council | Statement: [Mitcham and Morden, governingBorough, Merton London Borough Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBorough Context triple: [Mitcham and Morden, governingBorough, Merton London Borough Council]
-
A.
governingBoroughSeat
Indicates that one entity serves as the administrative seat or central governing location for a particular borough.
-
B.
hasLondonBorough
Indicates that an entity includes, contains, or is associated with a specific London borough as one of its administrative subdivisions.
-
C.
premiereBorough
Indicates the borough in which a work (such as a film, play, or performance) had its first public premiere.
-
D.
hasBoroughCouncil
chosen
Indicates that an administrative area is governed or overseen by a specific borough council.
-
E.
parliamentaryBoroughType
Indicates the specific classification or category of a parliamentary borough within a parliamentary or electoral system.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 21, 2026, 2:11 p.m.