Triple
T35870164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Historic Bungalow Initiative |
E1037200
|
entity |
| Predicate | buildingTypeFocus |
P156542
|
FINISHED |
| Object | single-family homes |
—
|
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: single-family homes | Statement: [Chicago Historic Bungalow Initiative, buildingTypeFocus, single-family homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingTypeFocus Context triple: [Chicago Historic Bungalow Initiative, buildingTypeFocus, single-family homes]
-
A.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
buildingTypeAtCenter
Indicates that a specific type of building is located at the central position of a given area or spatial context.
-
C.
buildingTypeServed
chosen
Indicates the type of building that is served, supported, or catered to by a given entity or system.
-
D.
buildingRole
Indicates the functional role or purpose that a building serves within a given context or system.
-
E.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.