Triple
T32255883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jörg Winger |
E824020
|
entity |
| Predicate | hasCreatedWorkSetIn |
P118009
|
FINISHED |
| Object | East Germany |
—
|
NE NERFINISHED |
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: East Germany | Statement: [Jörg Winger, hasCreatedWorkSetIn, East Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatedWorkSetIn Context triple: [Jörg Winger, hasCreatedWorkSetIn, East Germany]
-
A.
hasNotableWorkSetThere
Indicates that a notable work (such as a book, film, or other creative piece) is set in or takes place within the referenced location.
-
B.
hasWorkCreator
chosen
Indicates that an entity is the creator or originator of a particular work (such as a document, artwork, or other creative product).
-
C.
hasWorkBasedOn
Indicates that one work is derived from, adapted from, or otherwise based on the content of another work.
-
D.
usedInWorkSetIn
Indicates that something (such as an element, motif, or device) is employed within a creative work whose narrative or content is set in a particular place or time.
-
E.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 12:41 a.m.