Triple
T14592622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RGS-IBG |
E342480
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kensington |
E14419
|
NE 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: Kensington | Statement: [RGS-IBG, locatedIn, Kensington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kensington Context triple: [RGS-IBG, locatedIn, Kensington]
-
A.
Kensington
chosen
Kensington is a district in West London, England, known for its affluent residential areas, cultural institutions, and royal associations.
-
B.
Kensington
Kensington is a small, affluent unincorporated community in Contra Costa County, California, located in the San Francisco Bay Area.
-
C.
Kensington
Kensington is a popular inner-city district in Calgary known for its vibrant mix of shops, restaurants, and cultural venues.
-
D.
Kensington
Kensington is a historic Philadelphia neighborhood known for its industrial past and ongoing urban redevelopment.
-
E.
Kensington
Kensington is a residential neighborhood in central Brooklyn, New York City, known for its diverse population and mix of apartment buildings and single-family homes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43480d8819084a707e56da2c237 |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda902c598819083c5373172ed758e |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 10, 2026, 1:24 a.m.