Triple
T13499142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann David Wyss |
E320837
|
entity |
| Predicate | notableWorkPublicationLanguage |
P104717
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Johann David Wyss, notableWorkPublicationLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkPublicationLanguage Context triple: [Johann David Wyss, notableWorkPublicationLanguage, German]
-
A.
notableWorkPublicationDate
Indicates the date on which a notable work associated with an entity was first published.
-
B.
notableWorkWrittenIn
chosen
Indicates that a notable work was written in a particular language, place, or time period.
-
C.
notableAuthorInLanguage
Indicates that a person is a particularly prominent or distinguished author who writes in the specified language.
-
D.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or context.
-
E.
notableWorkAs
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with an entity.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4fab688190bdc746985b0c7338 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.