Triple
T2864267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fishtown |
E63399
|
entity |
| Predicate | gentrificationBegan |
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: [Fishtown, gentrificationBegan, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gentrificationBegan Context triple: [Fishtown, gentrificationBegan, late 20th century]
-
A.
hasSuburbanGrowth
Indicates that an area or entity is experiencing or characterized by expansion or development typical of suburban environments.
-
B.
hasUrbanGrowthCharacteristic
Indicates that an entity exhibits a particular quality, pattern, or feature related to urban growth or expansion.
-
C.
urbanStatusSince
Indicates the point in time since which an entity has held an urban status or classification.
-
D.
urbanDevelopmentEra
chosen
Indicates the historical period or phase during which significant urban development or transformation of a place occurred.
-
E.
urbanRedevelopmentArea
Indicates that a location is designated for concentrated urban renewal activities such as redevelopment, revitalization, or land-use transformation.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb853908190aa2fd492e9fa5e87 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.