Triple
T5756414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Arsenal Riverside regeneration project |
E126978
|
entity |
| Predicate | reuses |
P47023
|
FINISHED |
| Object | historic Royal Arsenal buildings |
—
|
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: historic Royal Arsenal buildings | Statement: [Royal Arsenal Riverside regeneration project, reuses, historic Royal Arsenal buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reuses Context triple: [Royal Arsenal Riverside regeneration project, reuses, historic Royal Arsenal buildings]
-
A.
reusability
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
-
B.
usedRite
Indicates that an entity performed, followed, or applied a particular rite or ritual in some context.
-
C.
reiterates
Indicates that an entity repeats or restates something that was previously expressed, often to emphasize or clarify it.
-
D.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
E.
laterRepurposedFor
chosen
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029084e108190988f1b5f38254007 |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.