Triple
T31097955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnipro Dam |
E792586
|
entity |
| Predicate | SovietEraProject |
P171142
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dnipro Dam, SovietEraProject, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SovietEraProject Context triple: [Dnipro Dam, SovietEraProject, yes]
-
A.
sovietEraFunction
Indicates that the entity served a role, purpose, or operational function specifically during the Soviet era.
-
B.
SovietAction
Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward another entity.
-
C.
sovietPeriodName
Indicates that the object is the name used for the subject during the Soviet period.
-
D.
sovietHistory
Indicates a relationship where an entity is associated with, pertains to, or is characterized by the history of the Soviet Union.
-
E.
SovietFront
Indicates a military relationship where a unit, operation, or event is associated with or occurs on a Soviet military front (a major wartime operational formation).
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6e0b888190a417ae712c42db0d |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:03 p.m.