Triple
T12278308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primetime Emmy Awards for acting |
E292648
|
entity |
| Predicate | hasGuestRoleCategories |
P82611
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Primetime Emmy Awards for acting, hasGuestRoleCategories, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuestRoleCategories Context triple: [Primetime Emmy Awards for acting, hasGuestRoleCategories, yes]
-
A.
hasTicketCategory
Indicates that an item, event, or access right is associated with a specific ticket category or type.
-
B.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
-
C.
hasCategories
chosen
Indicates that an entity is associated with one or more categories that classify or group it.
-
D.
includesGuestTeams
Indicates that an entity contains or involves one or more teams designated as guests within its scope or composition.
-
E.
hasCategoryGroup
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.