Triple
T29415642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York Street (Ottawa) |
E746018
|
entity |
| Predicate | hasTimeUsePattern |
P70126
|
FINISHED |
| Object | daytime shopping |
—
|
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: daytime shopping | Statement: [York Street (Ottawa), hasTimeUsePattern, daytime shopping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeUsePattern Context triple: [York Street (Ottawa), hasTimeUsePattern, daytime shopping]
-
A.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
-
B.
hasTypicalUseTime
chosen
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
C.
hasTimeOptions
Indicates that an entity is associated with one or more selectable time choices or configurations.
-
D.
screenTimePattern
Indicates how an entity’s use of screens (such as duration, frequency, or timing) is distributed or structured over a given period.
-
E.
usesTimingRules
Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 28, 2026, 3:01 p.m.