Triple
T30824478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hard to Be a God |
E785015
|
entity |
| Predicate | postProductionCompletedAfterDirectorDeath |
P170543
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hard to Be a God, postProductionCompletedAfterDirectorDeath, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postProductionCompletedAfterDirectorDeath Context triple: [Hard to Be a God, postProductionCompletedAfterDirectorDeath, true]
-
A.
directorWhoRemained
Indicates that a person is the director who continued in their role or position over a specified period or through a particular change or event.
-
B.
directorEnd
Indicates that a person’s role as a director of an entity has concluded at a specified time or event.
-
C.
workedAsDirectorFor
Indicates that one entity held the role of director in relation to another entity, such as an organization, project, or production.
-
D.
laterProduction
Indicates that one production event or version occurs after another in time.
-
E.
firstProductionDirector
Indicates that the object is the person who first served as production director for the subject.
- F. None of above. chosen
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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690f4e10c8190a3c68f9827c0f2a9 |
completed | May 3, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:44 p.m.