Triple
T36631110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EH10 |
E904317
|
entity |
| Predicate | containsResidentialAreas |
P9064
|
FINISHED |
| Object | suburban housing |
—
|
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: suburban housing | Statement: [EH10, containsResidentialAreas, suburban housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsResidentialAreas Context triple: [EH10, containsResidentialAreas, suburban housing]
-
A.
hasResidentialArea
chosen
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
B.
hasUpscaleResidentialArea
Indicates that a location contains or is associated with a high-end, affluent residential neighborhood or district.
-
C.
isInResidentialArea
Indicates that something is located within a residential area, such as a neighborhood or zone primarily designated for housing.
-
D.
hasQuietResidentialAreas
Indicates that a place includes neighborhoods characterized by low noise levels and a calm, residential atmosphere.
-
E.
hasResidentialBuilding
Indicates that an entity possesses, contains, or is associated with a residential building as part of its properties or components.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a013c50bcb8819086d163f1a796a9b8 |
completed | May 11, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_6a013c01bac88190b15c70910c02a8a7 |
completed | May 11, 2026, 2:16 a.m. |
Created at: May 3, 2026, 4:11 p.m.