Triple
T14002700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Village (Chicago) |
E336868
|
entity |
| Predicate | hasHousingMarketCharacteristic |
P9356
|
FINISHED |
| Object | rising property values |
—
|
LITERAL FINISHED |
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: rising property values | Statement: [East Village (Chicago), hasHousingMarketCharacteristic, rising property values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHousingMarketCharacteristic Context triple: [East Village (Chicago), hasHousingMarketCharacteristic, rising property values]
-
A.
hasEconomyCharacteristic
Indicates that an economy possesses a particular attribute, feature, or quality.
-
B.
neighborhoodCharacteristic
chosen
Indicates that a particular characteristic, feature, or quality is associated with or describes a given neighborhood.
-
C.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
D.
propertyMarket
Indicates a relationship where real estate or properties are being offered, traded, or evaluated within a market context.
-
E.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed06a50819093ddc64f55050689 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.