Triple
T31393301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 66th Primetime Emmy Awards |
E800793
|
entity |
| Predicate | eligibilityPeriodStart |
P16413
|
FINISHED |
| Object | 2013-06-01 |
—
|
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: 2013-06-01 | Statement: [66th Primetime Emmy Awards, eligibilityPeriodStart, 2013-06-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityPeriodStart Context triple: [66th Primetime Emmy Awards, eligibilityPeriodStart, 2013-06-01]
-
A.
eligibilityPeriodStartYear
Indicates the calendar year in which an entity’s eligibility period begins.
-
B.
eligibilityPeriod
chosen
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
C.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
D.
pensionStartDate
Indicates the date on which a person’s pension benefits begin to accrue or be paid.
-
E.
grantPeriodStart
Indicates the date or time at which a grant’s active period or coverage begins.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 9:19 p.m.