Triple
T4301415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytime Emmy Award for Outstanding Lead Actor in a Drama Series |
E99844
|
entity |
| Predicate | leadOrSupporting |
P15292
|
FINISHED |
| Object | lead |
—
|
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: lead | Statement: [Daytime Emmy Award for Outstanding Lead Actor in a Drama Series, leadOrSupporting, lead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadOrSupporting Context triple: [Daytime Emmy Award for Outstanding Lead Actor in a Drama Series, leadOrSupporting, lead]
-
A.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
B.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
-
C.
leadSingle
chosen
Indicates that an entity serves as the primary or featured performer, contributor, or focus in a single work or instance.
-
D.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
E.
helpsLead
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509fb2b88190a13ab88a5b924052 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.