Triple
T9120975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 105 Victoria Street |
E218846
|
entity |
| Predicate | hasRedevelopmentStartYear |
P42665
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [105 Victoria Street, hasRedevelopmentStartYear, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRedevelopmentStartYear Context triple: [105 Victoria Street, hasRedevelopmentStartYear, 2022]
-
A.
redevelopmentStartDate
chosen
Indicates the date on which a redevelopment project or process officially begins.
-
B.
hasRedevelopmentProgram
Indicates that an entity is subject to or involved in a planned process of redevelopment, typically through an organized program or initiative.
-
C.
majorRedevelopmentPeriod
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
D.
hasRedevelopmentGoal
Indicates that an entity is associated with a specific objective or target related to redevelopment or renewal activities.
-
E.
redevelopmentInvolved
Indicates that an entity participated in or was associated with the process of redeveloping another entity, such as land, property, or infrastructure.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b32ba88190b2b4406c7b905cca |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.