Triple
T24563865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Pride Fest |
E607730
|
entity |
| Predicate | heldInNeighborhood |
P104937
|
FINISHED |
| Object | Boystown |
—
|
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: Boystown | Statement: [Chicago Pride Fest, heldInNeighborhood, Boystown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldInNeighborhood Context triple: [Chicago Pride Fest, heldInNeighborhood, Boystown]
-
A.
operatedInNeighborhood
chosen
Indicates that an entity conducted its activities or operations within a specific neighborhood.
-
B.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
C.
originatedInNeighborhood
Indicates that an entity began, was founded, or first came into existence within a specific neighborhood.
-
D.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
E.
partOfNeighborhoodNetwork
Indicates that an entity belongs to, or is included within, a specific neighborhood’s interconnected network or 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f8a7488190a11f32014539a4a3 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.