Triple
T32828597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Ring Suburbs of Atlanta |
E839624
|
entity |
| Predicate | typicalHousingTypes |
P119140
|
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: [Inner Ring Suburbs of Atlanta, typicalHousingTypes, single-family homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHousingTypes Context triple: [Inner Ring Suburbs of Atlanta, typicalHousingTypes, single-family homes]
-
A.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
B.
typeOfHouse
chosen
Indicates the specific category or kind of house associated with an entity (e.g., apartment, detached house, townhouse).
-
C.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
D.
typicalLotType
Indicates that one entity is the standard or commonly occurring type of lot associated with another entity.
-
E.
domicileType
Indicates the category or kind of residence or dwelling associated with an entity.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:16 a.m.