Triple
T25237561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windrush generation |
E632379
|
entity |
| Predicate | typicalSettlementCity |
P136309
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [Windrush generation, typicalSettlementCity, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSettlementCity Context triple: [Windrush generation, typicalSettlementCity, London]
-
A.
typicalSettlement
Indicates that the subject is a common or characteristic type of settlement typically found in the context of the object.
-
B.
settlementCity
Indicates that a settlement is located within or corresponds to a particular city.
-
C.
usualCity
chosen
Indicates that a city is the standard, typical, or commonly associated city for a given entity (such as a person, organization, or activity).
-
D.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
E.
typicalVenueCity
Indicates that a particular city is the usual or standard location where an event, activity, or organization is typically held or based.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 21, 2026, 1:07 p.m.