Triple
T10566744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Heights, Chicago |
E249368
|
entity |
| Predicate | hasNotableHousingType |
P542
|
FINISHED |
| Object | Chicago bungalows |
—
|
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: Chicago bungalows | Statement: [Washington Heights, Chicago, hasNotableHousingType, Chicago bungalows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableHousingType Context triple: [Washington Heights, Chicago, hasNotableHousingType, Chicago bungalows]
-
A.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
-
B.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
C.
hasHouseWithin
Indicates that one entity possesses or is associated with a house that is located within the spatial or administrative boundaries of another entity.
-
D.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
E.
hasHousingPolicy
Indicates that an entity possesses, adopts, or is governed by a specific housing-related policy or set of rules.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5272ef5848190b76d671ea2d26314 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:36 p.m.