Triple
T261718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter Parade and Bonnet Festival |
E5554
|
entity |
| Predicate | typicalTimeOfDay |
P6019
|
FINISHED |
| Object | morning |
—
|
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: morning | Statement: [Easter Parade and Bonnet Festival, typicalTimeOfDay, morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimeOfDay Context triple: [Easter Parade and Bonnet Festival, typicalTimeOfDay, morning]
-
A.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
B.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
hasTimeOfDay
chosen
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
-
D.
typicalBusinessHourStartLocalTime
Indicates the local time at which a business’s normal operating hours typically begin.
-
E.
budTime
Indicates the time or period when a bud forms or begins to develop.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b6c968c819094fc903a3a377e15 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.