Triple
T38237062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elisabeth (musical) – composer |
E1013649
|
entity |
| Predicate | roleForWork |
P190192
|
FINISHED |
| Object | Elisabeth (musical) |
—
|
NE NERFINISHED |
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: Elisabeth (musical) | Statement: [Elisabeth (musical) – composer, roleForWork, Elisabeth (musical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleForWork Context triple: [Elisabeth (musical) – composer, roleForWork, Elisabeth (musical)]
-
A.
socialRoleInWork
Indicates the role or position an entity holds within a work-related or professional social context.
-
B.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
inUniverseWorkplaceRole
Indicates that an entity holds a specific workplace role or job position within a fictional or narrative universe.
-
E.
roleOfPerson
Indicates that a specific role, function, or position is assigned to or held by a particular person.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc330b4288190858b49d986160706 |
completed | May 7, 2026, 4:52 p.m. |
Created at: May 3, 2026, 4:30 p.m.