Triple
T1981275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonia Roma |
E43029
|
entity |
| Predicate | demographicsTrend |
P31774
|
FINISHED |
| Object | gentrification |
—
|
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: gentrification | Statement: [Colonia Roma, demographicsTrend, gentrification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demographicsTrend Context triple: [Colonia Roma, demographicsTrend, gentrification]
-
A.
demographics
Indicates the relationship of providing or characterizing statistical information about a population’s attributes, such as age, gender, income, or education.
-
B.
approximatePopulationTrend
chosen
Indicates an estimated or generalized pattern of how a population changes over time (e.g., increasing, decreasing, or stable) rather than an exact count.
-
C.
demographicsNote
Indicates that there is an associated note or commentary describing demographic-related information about an entity.
-
D.
demographicImpact
Indicates how an action, event, or condition affects the size, structure, or composition of a population.
-
E.
demographicsLabel
Indicates the categorical demographic group or segment that an entity is associated with or classified under.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.