Triple
T22138656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floatfest |
E547097
|
entity |
| Predicate | typicalTimingRelativeToEvent |
P6833
|
FINISHED |
| Object | immediately after the Rose Parade |
—
|
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: immediately after the Rose Parade | Statement: [Floatfest, typicalTimingRelativeToEvent, immediately after the Rose Parade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimingRelativeToEvent Context triple: [Floatfest, typicalTimingRelativeToEvent, immediately after the Rose Parade]
-
A.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
B.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
C.
commitmentTiming
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
-
D.
usesTimingRules
Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
-
E.
typicalDelay
Indicates the usual or expected amount of time by which something is delayed relative to its planned or nominal schedule.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bc7ae881909798c64a4c19adad |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.