Triple
T25588290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hjalmar Gullberg |
E641446
|
entity |
| Predicate | has literary form |
P6480
|
FINISHED |
| Object | poetry |
—
|
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: poetry | Statement: [Hjalmar Gullberg, has literary form, poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has literary form Context triple: [Hjalmar Gullberg, has literary form, poetry]
-
A.
hasLiteraryForm
chosen
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
B.
literaryFeature
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
-
C.
hasLiteraryMode
Indicates that a work, text, or expression is associated with a particular literary mode (such as satire, realism, or allegory) that characterizes its style or narrative approach.
-
D.
literaryGenreOfWork
Indicates that a work belongs to or is classified under a particular literary genre.
-
E.
literatureType
Indicates the specific category or genre of literature that characterizes or classifies a given work or text.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f96b32008190ad411ee7472c6b77 |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:18 p.m.