Triple
T31660561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avonside |
E807988
|
entity |
| Predicate | hasRebuildActivity |
P25491
|
FINISHED |
| Object | post-earthquake urban regeneration projects |
—
|
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: post-earthquake urban regeneration projects | Statement: [Avonside, hasRebuildActivity, post-earthquake urban regeneration projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRebuildActivity Context triple: [Avonside, hasRebuildActivity, post-earthquake urban regeneration projects]
-
A.
hasRebuilt
Indicates that an entity has restored, reconstructed, or built again something that previously existed or was damaged or destroyed.
-
B.
hasReconciliationActivities
Indicates that one entity engages in actions or processes aimed at restoring harmony, resolving conflicts, or repairing relationships with another entity.
-
C.
hasReprocessingActivity
Indicates that an entity engages in or is associated with an activity that reprocesses materials, resources, or products.
-
D.
hasRebuiltDate
Indicates the date on which something was rebuilt or reconstructed.
-
E.
haveReconstructionWork
chosen
Indicates that an entity is undergoing or is associated with reconstruction or restoration work.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a018c6b7178819097d5450a1e3c2408 |
completed | May 11, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_6a018a4f741c8190babe721a908e2f5e |
completed | May 11, 2026, 7:50 a.m. |
Created at: April 30, 2026, 10:57 p.m.