Triple
T2033219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welland Canal |
E44563
|
entity |
| Predicate | currentVersionOpened |
P617
|
FINISHED |
| Object | 1932 |
—
|
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: 1932 | Statement: [Welland Canal, currentVersionOpened, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVersionOpened Context triple: [Welland Canal, currentVersionOpened, 1932]
-
A.
currentVersionAdopted
Indicates that a specified version is the one presently in use or officially adopted by the relevant entity or system.
-
B.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
-
C.
currentCoreVersionEnactedIn
Indicates that a specific version of the core (e.g., a standard, framework, or core specification) is currently in force within a given context, jurisdiction, or system.
-
D.
openedIn
chosen
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.