Triple
T4385108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church and Wellesley |
E99222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | LGBTQ+ district |
C6755
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: LGBTQ+ district Context triple: [Church and Wellesley, instanceOf, LGBTQ+ district]
-
A.
LGBT district
chosen
An LGBT district is an urban neighborhood or area known for its concentration of lesbian, gay, bisexual, and transgender residents, businesses, cultural institutions, and nightlife, serving as a social and political hub for the LGBT community.
-
B.
LGBTQ+ pride event
An LGBTQ+ pride event is a public gathering or celebration that promotes visibility, acceptance, and rights for lesbian, gay, bisexual, transgender, queer, and other sexual and gender minority communities through parades, performances, speeches, and community activities.
-
C.
LGBT memorial
An LGBT memorial is a monument, site, or installation dedicated to honoring and remembering the lives, struggles, and contributions of lesbian, gay, bisexual, and transgender people, particularly those who have faced persecution, violence, or discrimination.
-
D.
LGBTQ+ awareness month
LGBTQ+ Awareness Month is a dedicated period of time focused on educating about LGBTQ+ identities and histories, promoting acceptance and inclusion, and advocating for the rights and well-being of LGBTQ+ individuals.
-
E.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
- F. None of above.
Provenance (1 batch)
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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:19 p.m.