Triple
T28802854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middleton, Idaho |
E727288
|
entity |
| Predicate | isGrowingResidentialCommunity |
P18321
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Middleton, Idaho, isGrowingResidentialCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGrowingResidentialCommunity Context triple: [Middleton, Idaho, isGrowingResidentialCommunity, true]
-
A.
residentialCommunity
Indicates that an entity is a residential community where people live, such as a neighborhood, housing complex, or similar residential area.
-
B.
isResidentialCommunityOn
Indicates that a residential community is located on or situated along a specified geographic feature, area, or infrastructure.
-
C.
isPlannedCommunity
Indicates that a community has been intentionally designed and developed according to a coordinated plan rather than growing organically.
-
D.
isGrowingCommunity
chosen
Indicates that a community is increasing in size, activity, or engagement over time.
-
E.
hasSuburbanGrowth
Indicates that an area or entity is experiencing or characterized by expansion or development typical of suburban environments.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:27 a.m.