Triple
T14732494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oreste in Hadestown |
E346111
|
entity |
| Predicate | isRoleFor |
P11687
|
FINISHED |
| Object | male performer |
—
|
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: male performer | Statement: [Oreste in Hadestown, isRoleFor, male performer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRoleFor Context triple: [Oreste in Hadestown, isRoleFor, male performer]
-
A.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
isAuthorityFor
Indicates that one entity holds recognized power, control, or decision-making responsibility over another entity or domain.
-
C.
isGrantedFor
Indicates that a permission, right, or benefit has been formally given to a specific entity for a particular purpose or use.
-
D.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec72ea9348190817efcdaa973d7f7 |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:29 a.m.