Triple
T6203056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagan Canal |
E138681
|
entity |
| Predicate | restorationEfforts |
P44155
|
FINISHED |
| Object | ongoing |
—
|
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: ongoing | Statement: [Lagan Canal, restorationEfforts, ongoing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationEfforts Context triple: [Lagan Canal, restorationEfforts, ongoing]
-
A.
revitalizationEffort
Indicates efforts or actions undertaken to restore, renew, or improve the condition, vitality, or functionality of something.
-
B.
restorationEvent
Indicates an event in which something previously altered, damaged, or degraded is returned to a former or improved state.
-
C.
restorationMeasure
Indicates that an action or intervention is undertaken to repair, rehabilitate, or return something to a previous or improved state.
-
D.
restorationProject
chosen
Indicates a project whose purpose is to repair, renew, or return something to a previous or improved condition.
-
E.
restorationGoal
Indicates that an action or plan is intended to return something to a previous, original, or improved state or condition.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626a32908190a3332008aee2e4a9 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.