Triple
T10381650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Edward Viaduct |
E244654
|
entity |
| Predicate | LuminousVeilOpeningDate |
P8984
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Prince Edward Viaduct, LuminousVeilOpeningDate, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LuminousVeilOpeningDate Context triple: [Prince Edward Viaduct, LuminousVeilOpeningDate, 2003]
-
A.
unveiledOn
chosen
Indicates the date or event at which something (such as a product, artwork, or plan) was formally revealed or made public.
-
B.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
C.
phase1OpeningDate
Indicates the date on which the first phase of a project, development, or initiative is officially opened or begins operation.
-
D.
rolloutDate
Indicates the date on which something (such as a product, feature, or policy) is first introduced or made available for general use.
-
E.
openingDateLine14
Indicates the date on which something (such as a service, facility, or record) is opened or begins operation, as specified in line 14 of a form or document.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9921fa48190a874aa9a9e385b97 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.