Triple
T33695164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago art scene |
E863282
|
entity |
| Predicate | hasNeighborhoodHub |
P200345
|
FINISHED |
| Object | River North |
—
|
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: River North | Statement: [Chicago art scene, hasNeighborhoodHub, River North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighborhoodHub Context triple: [Chicago art scene, hasNeighborhoodHub, River North]
-
A.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
B.
hasNeighborhoodCluster
Indicates that one area or location is grouped within a specific neighborhood cluster based on spatial or community-related characteristics.
-
C.
hasNeighborhoodBase
Indicates that one topological space has a specified collection of neighborhoods at each point that forms a neighborhood base for its topology.
-
D.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
E.
hasNeighborhoodRole
Indicates that an entity holds a specific role, function, or position within a neighborhood or local community context.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_69ff841f2f2081908d72d4f878c538a0 |
completed | May 9, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:43 a.m.