Triple
T31945118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna |
E815628
|
entity |
| Predicate | stageWorkForm |
P173478
|
FINISHED |
| Object | five-act opera |
—
|
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: five-act opera | Statement: [Anna, stageWorkForm, five-act opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageWorkForm Context triple: [Anna, stageWorkForm, five-act opera]
-
A.
stagedWorkBy
Indicates that a particular staging or production of a work (such as a play, opera, or performance) was created, directed, or otherwise realized by a specific person or organization.
-
B.
stageAdaptationForm
Indicates that one work is a stage adaptation (e.g., play, musical, performance script) derived from another work.
-
C.
stageProduction
Indicates that an entity organizes and presents a live performance or show, typically involving planning, rehearsing, and mounting the production for an audience.
-
D.
stageModel
Indicates a relationship where one entity serves as or defines the staging or intermediate version of a model for another entity.
-
E.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:06 a.m.