Triple
T25777509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashby Canal |
E649192
|
entity |
| Predicate | hasRestorationBody |
P141552
|
FINISHED |
| Object | Ashby Canal Association |
—
|
NE NERFINISHED |
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: Ashby Canal Association | Statement: [Ashby Canal, hasRestorationBody, Ashby Canal Association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestorationBody Context triple: [Ashby Canal, hasRestorationBody, Ashby Canal Association]
-
A.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
B.
hasUseAfterRestoration
Indicates that an entity is used or has a function specifically after it has been restored or repaired.
-
C.
hasRestorationGroup
chosen
Indicates that an entity is associated with a group responsible for its repair, conservation, or restoration.
-
D.
hasBeenRestored
Indicates that an entity has been returned to a previous or original state after damage, loss, or alteration.
-
E.
hasRestorationApproach
Indicates the method or strategy used to restore or rehabilitate something to a desired state.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 22, 2026, 5:35 a.m.