Triple
T31393325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 66th Primetime Emmy Awards |
E800793
|
entity |
| Predicate | redCarpetCoverage |
P147660
|
FINISHED |
| Object | E! |
—
|
NE NERFINISHED |
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: E! | Statement: [66th Primetime Emmy Awards, redCarpetCoverage, E!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redCarpetCoverage Context triple: [66th Primetime Emmy Awards, redCarpetCoverage, E!]
-
A.
brandCovered
chosen
Indicates that one entity provides coverage, representation, or inclusion for a particular brand within its scope (e.g., in a policy, service, catalog, or offering).
-
B.
eraCovered
Indicates that one entity temporally encompasses, includes, or spans the historical period or era associated with another entity.
-
C.
reignCoverage
Indicates the temporal span or extent over which a ruler’s reign or authority is in effect.
-
D.
stageCoverage
Indicates that one entity provides or has coverage, representation, or support for another within a particular stage or phase of a process or workflow.
-
E.
trackCoveredBy
Indicates that one track or path is physically overlaid, shielded, or enclosed by another structure or material.
- 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_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.