Triple
T33352714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantazy |
E853986
|
entity |
| Predicate | isPartOfWorkOf |
P84659
|
FINISHED |
| Object | Juliusz Słowacki dramatic oeuvre |
—
|
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: Juliusz Słowacki dramatic oeuvre | Statement: [Fantazy, isPartOfWorkOf, Juliusz Słowacki dramatic oeuvre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfWorkOf Context triple: [Fantazy, isPartOfWorkOf, Juliusz Słowacki dramatic oeuvre]
-
A.
isPartOfBodyOfWork
Indicates that one creative work is a component, segment, or installment within a larger overarching body of related work.
-
B.
partOfWorkType
Indicates that something is a component, subtype, or specific category within a broader type of work.
-
C.
partOfLargerWorkByAuthor
chosen
Indicates that a work is a component or section of a larger work created by the same author.
-
D.
hasPartInCreativeOutput
Indicates that an entity contributed a component, role, or involvement to the creation or production of a particular creative work.
-
E.
coverOfWorkBy
Indicates that one work is a cover version or performance of another work originally created by a specified creator or artist.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 1, 2026, 1:34 a.m.