Triple
T38434587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zollikon seminars with Martin Heidegger |
E903904
|
entity |
| Predicate | editorOfDocumentation |
P107303
|
FINISHED |
| Object | Medard Boss |
—
|
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: Medard Boss | Statement: [Zollikon seminars with Martin Heidegger, editorOfDocumentation, Medard Boss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorOfDocumentation Context triple: [Zollikon seminars with Martin Heidegger, editorOfDocumentation, Medard Boss]
-
A.
editorOfWork
chosen
Indicates that one entity serves as the editor responsible for preparing, revising, or overseeing the content of a particular work.
-
B.
editedBy
Indicates that one entity has revised, modified, or otherwise made editorial changes to another entity.
-
C.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
D.
editorCommunity
Indicates a relationship where an editor is associated with, participates in, or belongs to a particular community.
-
E.
editorName
Indicates the relationship that specifies the name of an editor associated with a given 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.