Triple
T17696306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werke in Einzelausgaben: Komödien |
E441179
|
entity |
| Predicate | workCollectionType |
P108224
|
FINISHED |
| Object | individually published plays |
—
|
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: individually published plays | Statement: [Werke in Einzelausgaben: Komödien, workCollectionType, individually published plays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCollectionType Context triple: [Werke in Einzelausgaben: Komödien, workCollectionType, individually published plays]
-
A.
workCollectionTitle
Indicates the title assigned to a collection of works associated with an entity.
-
B.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
C.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
D.
worksCollectedAs
chosen
Indicates that multiple individual works are gathered, compiled, or published together as a single collected entity.
-
E.
workTypeContributedTo
Indicates that an entity contributed to the creation, development, or production of a particular type of 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47156a8f8819080cc730f4e9bc6ad |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:04 a.m.