Triple
T32411628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taste of Soulard |
E828236
|
entity |
| Predicate | neighborhoodShowcased |
P113268
|
FINISHED |
| Object | Soulard historic district |
—
|
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: Soulard historic district | Statement: [Taste of Soulard, neighborhoodShowcased, Soulard historic district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighborhoodShowcased Context triple: [Taste of Soulard, neighborhoodShowcased, Soulard historic district]
-
A.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
B.
neighborhoodView
Indicates that an entity has a view overlooking or prominently featuring the surrounding neighborhood or nearby residential area.
-
C.
depictsNeighborhood
chosen
Indicates that one entity visually represents or portrays the neighborhood or local area associated with another entity.
-
D.
notableNeighborhoodType
Indicates that a neighborhood is notably characterized by, or strongly associated with, a particular type or category (e.g., residential, commercial, historic).
-
E.
typicalNeighborhoods
Indicates that the associated neighborhoods are characteristic or commonly found examples for the given entity or context.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 12:53 a.m.