Triple
T14406543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakhmut |
E357210
|
entity |
| Predicate | sovietPeriodName |
P114128
|
FINISHED |
| Object | Artemivsk (1924–2016) |
—
|
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: Artemivsk (1924–2016) | Statement: [Bakhmut, sovietPeriodName, Artemivsk (1924–2016)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovietPeriodName Context triple: [Bakhmut, sovietPeriodName, Artemivsk (1924–2016)]
-
A.
roleInSovietUnion
Indicates that an entity held a specific position, function, or status within the governmental, political, or institutional structure of the Soviet Union.
-
B.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
-
C.
hasSovietLeaderParticipant
Indicates that a Soviet leader is a participant in the referenced event, action, or relationship.
-
D.
homeCountryDuringSovietEra
Indicates the country that was considered an entity’s home country during the period of the Soviet Union’s existence.
-
E.
operatedInPoliticalPeriod
Indicates that an entity carried out its activities or functions during a specified political period or regime.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908804048190a4fe58afc2e0a5b6 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa1b57881909a033eac8545c417 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:17 a.m.