Triple
T25307776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily 3 |
E634526
|
entity |
| Predicate | ticketExpirationPeriod |
P41643
|
FINISHED |
| Object | 180 days from draw date |
—
|
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: 180 days from draw date | Statement: [Daily 3, ticketExpirationPeriod, 180 days from draw date]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketExpirationPeriod Context triple: [Daily 3, ticketExpirationPeriod, 180 days from draw date]
-
A.
typicalExpirationPeriod
chosen
Indicates the usual length of time after which something is expected to expire or become invalid.
-
B.
existencePeriod
Indicates the time span during which an entity exists or is valid.
-
C.
ticketValidityCovers
Indicates that the validity period or scope of a ticket extends to and includes a specified time, location, service, or condition.
-
D.
validityPeriodEnd
Indicates the date and time at which a previously valid state, authorization, or condition ceases to be valid.
-
E.
registrationPeriod
Indicates the time span during which registration for something is open or valid.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:25 p.m.