Triple
T17825391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection (1912 film) |
E445101
|
entity |
| Predicate | hasSourceAuthorNationality |
P6689
|
FINISHED |
| Object | Russian |
—
|
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: Russian | Statement: [Resurrection (1912 film), hasSourceAuthorNationality, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceAuthorNationality Context triple: [Resurrection (1912 film), hasSourceAuthorNationality, Russian]
-
A.
sourceWorkNationality
Indicates that a work or source is associated with a particular nationality or country of origin.
-
B.
authorNationality
chosen
Indicates the relationship between an author and the country or nationality with which that author is identified.
-
C.
hasCompilerNationality
Indicates that the compiler of a work or collection has a specific nationality.
-
D.
originalAuthorLaterNationality
Indicates that the original author of a work later acquired or changed to the specified nationality.
-
E.
coAuthorNationality
Indicates that two or more co-authors of a work share the same nationality or have nationalities being related in the context of their co-authorship.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48914226c819083edcc78e00b2d42 |
completed | April 19, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:15 a.m.