Triple
T5095846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennet and Avon Canal |
E114860
|
entity |
| Predicate | restorationBegan |
P37088
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Kennet and Avon Canal, restorationBegan, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationBegan Context triple: [Kennet and Avon Canal, restorationBegan, 1950s]
-
A.
restorationEnd
Indicates the point in time or condition at which a restoration process or restorative state comes to an end.
-
B.
attemptedRestoration
Indicates an action where an entity makes an effort to restore or return another entity to a previous or desired state, condition, or form, regardless of whether the restoration succeeds.
-
C.
preservationOperationsBegan
chosen
Indicates that actions or processes aimed at preserving or safeguarding something have been initiated.
-
D.
restorationEvent
Indicates an event in which something previously altered, damaged, or degraded is returned to a former or improved state.
-
E.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75652a8081908386718f1fdb1de3 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.