Triple
T654300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primetime Emmy Award for Outstanding Lead Actor in a Drama Series |
E11612
|
entity |
| Predicate | hasAwardComponent |
P486
|
FINISHED |
| Object | statuette |
—
|
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: statuette | Statement: [Primetime Emmy Award for Outstanding Lead Actor in a Drama Series, hasAwardComponent, statuette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAwardComponent Context triple: [Primetime Emmy Award for Outstanding Lead Actor in a Drama Series, hasAwardComponent, statuette]
-
A.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
-
B.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
C.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
-
D.
typicalAwardComponents
chosen
Indicates the standard elements or parts that commonly make up a particular award.
-
E.
hasSubsequentAward
Indicates that an entity has received an additional award that follows a previous award in time or sequence.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4bb5b881908a18b5ec1c94e0cf |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d1001088190aa7ca3c8f2ad0e32 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.