Triple
T31370849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nils Sjöberg |
E800156
|
entity |
| Predicate | pseudonymForRole |
P171275
|
FINISHED |
| Object | songwriter |
—
|
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: songwriter | Statement: [Nils Sjöberg, pseudonymForRole, songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pseudonymForRole Context triple: [Nils Sjöberg, pseudonymForRole, songwriter]
-
A.
nicknameForRole
Indicates that one entity is an informal or alternative name commonly used to refer to a particular role or position represented by another entity.
-
B.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
C.
addresseePseudonym
Indicates that the referenced name is a pseudonym used for the addressee in the context of the described communication or interaction.
-
D.
pseudonymInspiredBy
Indicates that a pseudonym was chosen or created based on, or in homage to, another name, person, work, or concept.
-
E.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
- F. None of above. chosen
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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f89a7f881909b2eaca8904ba555 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69ea761848190acb31298e65b7892 |
completed | May 3, 2026, 1:02 a.m. |
Created at: April 29, 2026, 9:18 p.m.