Triple
T32742118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection |
E837243
|
entity |
| Predicate | associatedWithTextAuthor |
P84740
|
FINISHED |
| Object | Friedrich Gottlieb Klopstock |
E142005
|
NE 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: Friedrich Gottlieb Klopstock | Statement: [Resurrection, associatedWithTextAuthor, Friedrich Gottlieb Klopstock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTextAuthor Context triple: [Resurrection, associatedWithTextAuthor, Friedrich Gottlieb Klopstock]
-
A.
actualAuthorOfAssociatedText
Indicates that an entity is the real creator or writer of a given associated text, regardless of how the text is attributed elsewhere.
-
B.
associatedWithText
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
-
C.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
D.
associatedWithAuthorRole
chosen
Indicates that an entity is connected to another entity specifically in the capacity or role of an author.
-
E.
associatedWithAuthorType
Indicates that one entity has a specified type of association or role in relation to an author.
- F. None of above.
Provenance (4 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34a7ae03a88190a5bbc6798edfe56a |
completed | June 19, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:12 a.m.