Triple
T6980137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langworthy |
E161820
|
entity |
| Predicate | urbanRegenerationType |
P5744
|
FINISHED |
| Object | housing renewal |
—
|
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: housing renewal | Statement: [Langworthy, urbanRegenerationType, housing renewal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanRegenerationType Context triple: [Langworthy, urbanRegenerationType, housing renewal]
-
A.
urbanRegenerationStatus
Indicates the current stage or condition of efforts to renew, redevelop, or revitalize an urban area.
-
B.
urbanRedevelopmentArea
Indicates that a location is designated for concentrated urban renewal activities such as redevelopment, revitalization, or land-use transformation.
-
C.
urbanDevelopmentType
chosen
Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
-
D.
urbanAdaptation
Indicates how well an entity adjusts its behavior, structure, or function to survive and operate effectively in urban environments.
-
E.
urbanDesignType
Indicates the specific category or style of urban design that characterizes or is applied to a place or project.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6c1efc8190ab1575ae2ce726db |
completed | March 27, 2026, 7:33 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.