Triple
T11712690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artaserse |
E278410
|
entity |
| Predicate | librettoStructure |
P86551
|
FINISHED |
| Object | three acts |
—
|
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: three acts | Statement: [Artaserse, librettoStructure, three acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: librettoStructure Context triple: [Artaserse, librettoStructure, three acts]
-
A.
librettoStyle
Indicates the stylistic characteristics or manner in which a libretto (the text of an opera or similar work) is written or composed.
-
B.
librettoBy
Indicates that a work’s libretto (the text of an opera or similar vocal work) was written by a particular person.
-
C.
includesLibretto
Indicates that one entity (typically a musical or operatic work or publication) contains or is accompanied by the full text/libretto of another work.
-
D.
hasDramaticStructure
chosen
Indicates that something possesses or follows a specific dramatic structure, such as an organized sequence of narrative or theatrical elements (e.g., exposition, climax, resolution).
-
E.
originalLanguageOfLibretto
Indicates the language in which a libretto was originally written for a given work.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4be10088190854699385d1f6a95 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.