Triple
T20398227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meet Me After the Show |
E500262
|
entity |
| Predicate | leadRoleType |
P5518
|
FINISHED |
| Object | Broadway star |
—
|
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: Broadway star | Statement: [Meet Me After the Show, leadRoleType, Broadway star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadRoleType Context triple: [Meet Me After the Show, leadRoleType, Broadway star]
-
A.
leadActorRolePattern
Indicates a recurring or characteristic type of role that an actor typically plays as a leading performer in productions.
-
B.
selectsForLeadRole
Indicates that one entity chooses another entity to perform or occupy the primary or leading role in a production, project, or activity.
-
C.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
D.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
E.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798c2b28819092fab93f01218cde |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.