Triple
T8625325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seventeen Moments of Spring (1973 TV series) |
E204266
|
entity |
| Predicate | mainCharacterCoverRole |
P21567
|
FINISHED |
| Object | SS officer |
—
|
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: SS officer | Statement: [Seventeen Moments of Spring (1973 TV series), mainCharacterCoverRole, SS officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterCoverRole Context triple: [Seventeen Moments of Spring (1973 TV series), mainCharacterCoverRole, SS officer]
-
A.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
controllingCharacter
Indicates that one character exerts control, influence, or authority over another character.
-
C.
featuresProtagonistOccupation
chosen
Indicates that the work’s main character has a specified occupation or job role.
-
D.
mainThemeCharacter
Indicates that a character serves as the central or primary figure associated with the main theme of a work or narrative.
-
E.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.