Triple
T30983126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urbis, Manchester |
E789439
|
entity |
| Predicate | repurposingDate |
P35617
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Urbis, Manchester, repurposingDate, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repurposingDate Context triple: [Urbis, Manchester, repurposingDate, 2012]
-
A.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
B.
reenvisionedDate
chosen
Indicates the date on which something was newly reimagined, redesigned, or conceptually revised.
-
C.
redevelopedAfter
Indicates that one entity was redeveloped at a later time than, and as a subsequent phase or replacement to, another entity.
-
D.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
-
E.
rediscoveredAt
Indicates that an entity was found or identified again at a particular time or place after having been lost, forgotten, or unknown.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.