Triple
T38568208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kallio |
E928286
|
entity |
| Predicate | timePeriodOfGentrification |
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: [Kallio, timePeriodOfGentrification, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfGentrification Context triple: [Kallio, timePeriodOfGentrification, late 20th century]
-
A.
urbanPlanningPeriod
Indicates the specific span of time during which urban planning activities, policies, or projects are designed, implemented, or in effect.
-
B.
urbanStatusSince
Indicates the point in time since which an entity has held an urban status or classification.
-
C.
urbanDevelopmentEra
chosen
Indicates the historical period or phase during which significant urban development or transformation of a place occurred.
-
D.
majorRedevelopmentPeriod
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
E.
renovationPeriod
Indicates the time span during which an object, structure, or entity undergoes renovation or refurbishment.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:32 p.m.