Triple
T33793196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Borough of Kingston upon Thames |
E865990
|
entity |
| Predicate | isOuterLondonBorough |
P177707
|
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: [London Borough of Kingston upon Thames, isOuterLondonBorough, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOuterLondonBorough Context triple: [London Borough of Kingston upon Thames, isOuterLondonBorough, true]
-
A.
hasOuterLondonBorough
Indicates that an entity is associated with, located in, or administered by a borough that is part of Outer London.
-
B.
isInInnerLondon
Indicates that one location lies within the administrative area defined as Inner London.
-
C.
hasLondonBorough
Indicates that an entity includes, contains, or is associated with a specific London borough as one of its administrative subdivisions.
-
D.
isMetropolitanBorough
Indicates that an entity functions as a metropolitan borough, i.e., a local government district within a large urban area that has borough status.
-
E.
isCountyBorough
Indicates that the subject entity has the status or classification of a county borough in relation to the object entity.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:45 a.m.