Triple
T15092586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnside Viaduct |
E360456
|
entity |
| Predicate | refurbishmentWorkIncluded |
P8964
|
FINISHED |
| Object | replacement of deck |
—
|
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: replacement of deck | Statement: [Arnside Viaduct, refurbishmentWorkIncluded, replacement of deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refurbishmentWorkIncluded Context triple: [Arnside Viaduct, refurbishmentWorkIncluded, replacement of deck]
-
A.
refurbishedIn
Indicates that an entity has undergone restoration, repair, or renovation at a specific time or during a particular period.
-
B.
hasRenovation
Indicates that an entity has undergone, is undergoing, or is associated with a renovation process or renovation event.
-
C.
requiresRenovation
Indicates that an entity is in a condition that necessitates repair, updating, or refurbishment before it is suitable for normal use or standards.
-
D.
renovationCompleted
Indicates that a renovation process for an entity has been fully finished and is no longer in progress.
-
E.
renovationFeature
chosen
Indicates that an entity has a specific renovation-related characteristic, element, or improvement associated with it.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0027925788190b955fdc6626adf7d |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.