Triple
T28126351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drama Desk Award for Outstanding Actor in a Musical |
E710936
|
entity |
| Predicate | hasMultipleNominees |
P179207
|
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: [Drama Desk Award for Outstanding Actor in a Musical, hasMultipleNominees, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleNominees Context triple: [Drama Desk Award for Outstanding Actor in a Musical, hasMultipleNominees, yes]
-
A.
hasMultipleAwardsPossible
Indicates that an entity is eligible to receive or be associated with more than one award.
-
B.
hasNomineeRole
Indicates that an entity serves in or holds a specific nominee role or position in relation to another entity.
-
C.
hasNomineeType
Indicates that an entity has a nominee belonging to a specified type or category.
-
D.
nomineeOf
Indicates that one entity is a candidate put forward or selected for an award, position, or recognition by another entity.
-
E.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
- F. None of above. chosen
Provenance (4 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 27, 2026, 9:20 p.m.