Triple
T18734125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petitcodiac River |
E458115
|
entity |
| Predicate | hasRestorationAction |
P11189
|
FINISHED |
| Object | opening of causeway gates |
—
|
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: opening of causeway gates | Statement: [Petitcodiac River, hasRestorationAction, opening of causeway gates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestorationAction Context triple: [Petitcodiac River, hasRestorationAction, opening of causeway gates]
-
A.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
B.
hasRestorationApproach
Indicates the method or strategy used to restore or rehabilitate something to a desired state.
-
C.
hasRestorationActivities
chosen
Indicates that an entity carries out, is involved in, or is associated with actions aimed at restoring or rehabilitating another entity or resource.
-
D.
hasRestorationFocus
Indicates that something is primarily concerned with or directed toward restoration or repair.
-
E.
hasBeenRestored
Indicates that an entity has been returned to a previous or original state after damage, loss, or alteration.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d7a06788190a8e09c657aaeb8e5 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.