Triple
T29472658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Семнадцать мгновений весны |
E747553
|
entity |
| Predicate | странаПроисхождения |
P168152
|
FINISHED |
| Object | СССР |
—
|
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: СССР | Statement: [Семнадцать мгновений весны, странаПроисхождения, СССР]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: странаПроисхождения Context triple: [Семнадцать мгновений весны, странаПроисхождения, СССР]
-
A.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
-
B.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
C.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
D.
laterCountryOfOrigin
Indicates that an entity’s country of origin changed, and this predicate specifies the country that became its origin at a later time than a previously associated country.
-
E.
historicalOriginMeaning
Indicates that one entity explains the original historical source or derivational meaning of another entity.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 3:58 p.m.