Triple
T17695623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gesammelte Werke |
E441157
|
entity |
| Predicate | editorialForm |
P46396
|
FINISHED |
| Object | critical edition |
—
|
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: critical edition | Statement: [Gesammelte Werke, editorialForm, critical edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorialForm Context triple: [Gesammelte Werke, editorialForm, critical edition]
-
A.
editorialFormat
chosen
Indicates the specific editorial style, layout, or presentation format in which content is produced or published.
-
B.
editorialSupport
Indicates that one entity provides editorial assistance, guidance, or services to another entity or work.
-
C.
editorialControl
Indicates that one entity has the authority to direct, modify, or approve the content or presentation produced by another entity.
-
D.
editorialOffice
Indicates that an entity serves as or is associated with the editorial office responsible for managing editorial processes (such as review, editing, and publication decisions) for another entity.
-
E.
editorialStandard
Indicates that one entity defines, follows, or enforces a particular set of editorial rules, guidelines, or quality criteria in relation to another entity or content.
- 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_69e471559744819080b99081c90ab614 |
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.