Triple
T29853471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgengruß |
E758122
|
entity |
| Predicate | cycleOriginalPublisher |
P7323
|
FINISHED |
| Object | Tobias Haslinger |
—
|
NE NERFINISHED |
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: Tobias Haslinger | Statement: [Morgengruß, cycleOriginalPublisher, Tobias Haslinger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleOriginalPublisher Context triple: [Morgengruß, cycleOriginalPublisher, Tobias Haslinger]
-
A.
originalPublisherType
Indicates the type or category of the entity that first published or released the content.
-
B.
originallyPublishedBy
Indicates that one entity is the original publisher or issuing source responsible for first making another entity publicly available.
-
C.
reprintPublisher
Indicates that an entity serves as the publisher responsible for issuing a reprinted edition of a work.
-
D.
firstPublisher
chosen
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
E.
correctedEditionPublisher
Indicates that a publisher is responsible for issuing a corrected edition of a previously published 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 5:45 p.m.