Triple
T35568140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | György Köves |
E1027834
|
entity |
| Predicate | associatedWorkEnglishTitle |
P922
|
FINISHED |
| Object | Fatelessness |
E314733
|
NE 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: Fatelessness | Statement: [György Köves, associatedWorkEnglishTitle, Fatelessness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkEnglishTitle Context triple: [György Köves, associatedWorkEnglishTitle, Fatelessness]
-
A.
associatedWorkSubtitle
Indicates the subtitle of a related or associated work.
-
B.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
C.
appearsInWorkByTitle
Indicates that an entity appears in, is featured in, or is contained within a work identified by its title.
-
D.
associatedWork
chosen
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
E.
usedInWorkEnglishTitle
Indicates that something (such as a term, concept, or element) is used within a work whose title is given in English.
- F. None of above.
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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38683edf5c81909f2e1c36def2ff31 |
completed | June 21, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.