Triple
T31729255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnenflammen |
E809810
|
entity |
| Predicate | isStageWork |
P173478
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sonnenflammen, isStageWork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStageWork Context triple: [Sonnenflammen, isStageWork, true]
-
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.
isStagedBy
Indicates that something (such as a performance, event, or production) is organized, directed, or put on by a particular agent or entity.
-
C.
stageWorkForm
chosen
Indicates that one work is a staged or performance-oriented version or format derived from another work.
-
D.
usesStage
Indicates that one entity employs or operates on another entity at a particular phase or stage within a process or workflow.
-
E.
hasStageIn
Indicates a relationship where one entity occurs, exists, or takes place within a particular stage or phase of another process, lifecycle, or sequence.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 11:21 p.m.