Triple
T33827039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tradeston |
E866984
|
entity |
| Predicate | hasRegenerationFocus |
P206686
|
FINISHED |
| Object | waterfront redevelopment |
—
|
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: waterfront redevelopment | Statement: [Tradeston, hasRegenerationFocus, waterfront redevelopment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegenerationFocus Context triple: [Tradeston, hasRegenerationFocus, waterfront redevelopment]
-
A.
hasRegenerationStatus
Indicates the current state or condition of an entity’s regeneration process (e.g., whether and how it is being restored or renewed).
-
B.
hasRegenerationType
Indicates the specific kind or method of regeneration associated with an entity.
-
C.
hasRegenerationCycleWith
Indicates that two entities are linked by a recurring regeneration or renewal process that they undergo together or in relation to each other.
-
D.
hasRecoveryFocus
Indicates that something is oriented toward, concerned with, or designed to support a process of recovery.
-
E.
hasReconstructionFocus
Indicates that something is primarily concerned with or directed toward the process or goal of reconstruction.
- F. None of above. chosen
Provenance (4 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.