Triple
T13335493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sainte-Anne-de-Bellevue |
E317679
|
entity |
| Predicate | canalOpened |
P109074
|
FINISHED |
| Object | 1843 |
—
|
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: 1843 | Statement: [Sainte-Anne-de-Bellevue, canalOpened, 1843]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canalOpened Context triple: [Sainte-Anne-de-Bellevue, canalOpened, 1843]
-
A.
containsCanal
Indicates that one geographical or spatial entity has a canal located within its boundaries or interior.
-
B.
canalProject
Indicates that an entity is involved in, associated with, or designated as a canal construction or development project.
-
C.
canalClaim
Indicates a claim, assertion, or right asserted by one party regarding control, ownership, use, or status of a canal.
-
D.
openedInConnectionWith
Indicates that one entity was opened as a direct result of, or in association with, another specific event, action, or entity.
-
E.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
- F. None of above. chosen
Provenance (4 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cff44e08190b9583baf0b626e42 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99073e4708190843bda3a1ae78f43 |
completed | April 11, 2026, 12:06 a.m. |
Created at: April 9, 2026, 9:30 p.m.