Triple
T8316688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lottery |
E194721
|
entity |
| Predicate | timeOfFictionalEvent |
P11197
|
FINISHED |
| Object | June 27 |
—
|
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: June 27 | Statement: [The Lottery, timeOfFictionalEvent, June 27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfFictionalEvent Context triple: [The Lottery, timeOfFictionalEvent, June 27]
-
A.
fictionalTime
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
B.
basedOnFictionalDateIn
Indicates that something is derived from, inspired by, or determined using a fictional date occurring within a specified work, timeline, or fictional context.
-
C.
timeOfNarrative
chosen
Indicates the specific time or period during which the events of a narrative are set or unfold.
-
D.
setInFictionalYear
Indicates that the events or narrative of a work are situated in a specified fictional or non-real calendar year.
-
E.
timeJump
Indicates a discontinuous transition of an entity from one point in time to another, skipping the intervening duration.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f557a7881908adcf353f7297848 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.