Triple
T28949558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Vancouver from the North Shore |
E730969
|
entity |
| Predicate | notableTimeOfDay |
P147906
|
FINISHED |
| Object | sunset |
—
|
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: sunset | Statement: [City of Vancouver from the North Shore, notableTimeOfDay, sunset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTimeOfDay Context triple: [City of Vancouver from the North Shore, notableTimeOfDay, sunset]
-
A.
associatedTimeOfDay
chosen
Indicates the specific time of day during which an event, state, or relationship occurs or is most relevant.
-
B.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
-
C.
timeOfDayEmphasized
Indicates that a particular time of day is highlighted or given special prominence in relation to an event or situation.
-
D.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
E.
bestTimeOfDayToVisit
Indicates the time of day during which visiting something is considered most optimal or desirable.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a01c41dfe248190a68f4a262591b30f |
completed | May 11, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a01c375d14c8190a15bfa12623588a9 |
completed | May 11, 2026, 11:54 a.m. |
Created at: April 28, 2026, 8:42 a.m.