Triple
T10848479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowery |
E256076
|
entity |
| Predicate | gentrificationPeriod |
P34609
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Bowery, gentrificationPeriod, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gentrificationPeriod Context triple: [Bowery, gentrificationPeriod, late 20th century]
-
A.
urbanDevelopmentEra
chosen
Indicates the historical period or phase during which significant urban development or transformation of a place occurred.
-
B.
majorRedevelopmentPeriod
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
C.
urbanStatusSince
Indicates the point in time since which an entity has held an urban status or classification.
-
D.
segregationEra
Indicates a period or context in which entities are subject to racially discriminatory separation or unequal treatment under segregation policies.
-
E.
redevelopmentPeaked
Indicates that the intensity or extent of redevelopment activity has reached its highest point within a given period or context.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75114ca988190a0e730131adb2df0 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.