Triple
T32742378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Von der Jugend |
E837249
|
entity |
| Predicate | textAuthorRole |
P86337
|
FINISHED |
| Object | poetic adaptor |
—
|
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: poetic adaptor | Statement: [Von der Jugend, textAuthorRole, poetic adaptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textAuthorRole Context triple: [Von der Jugend, textAuthorRole, poetic adaptor]
-
A.
declaredRoleOfAuthor
chosen
Indicates that a specific role or capacity has been explicitly stated or assigned to an author in relation to a work or contribution.
-
B.
notableAuthorRole
Indicates that an entity holds a significant or distinguished role as an author in relation to another entity.
-
C.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
D.
literaryAgentRoleOfAuthor
Indicates that an entity serves as the literary agent representing a particular author in professional or contractual matters.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.