Triple
T13499149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann David Wyss |
E320837
|
entity |
| Predicate | notableWorkSetting |
P63425
|
FINISHED |
| Object | desert island |
—
|
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: desert island | Statement: [Johann David Wyss, notableWorkSetting, desert island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkSetting Context triple: [Johann David Wyss, notableWorkSetting, desert island]
-
A.
settingOfNotableWork
Indicates that a particular place or environment serves as the primary setting where a notable work (such as a book, film, or play) takes place.
-
B.
notableWorkSetHere
chosen
Indicates that a notable creative work is set in or takes place within the referenced location.
-
C.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
D.
notableWorkArea
Indicates the field or domain in which an entity’s significant work or contributions are primarily focused.
-
E.
notablePlaceOfWork
Indicates that there is a notable or significant place where the entity has worked or been employed.
- 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.