Triple
T33032761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sievierodonetsk |
E845212
|
entity |
| Predicate | receivedCityStatusIn |
P180829
|
FINISHED |
| Object | 1958 |
—
|
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: 1958 | Statement: [Sievierodonetsk, receivedCityStatusIn, 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedCityStatusIn Context triple: [Sievierodonetsk, receivedCityStatusIn, 1958]
-
A.
receivedIn
Indicates that something was obtained, accepted, or taken possession of within a particular context, location, or time frame.
-
B.
receivedTransmissionOf
Indicates that one entity has obtained or been sent a transmission (such as a message, signal, or data) originating from another entity.
-
C.
receivedPromiseAbout
Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
-
D.
receivedSign
Indicates that one entity has obtained or been given a sign (such as a signal, symbol, or indication) from another entity.
-
E.
receivedGraceFrom
Indicates that one entity has been granted or has obtained grace, favor, or unmerited kindness from 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: May 1, 2026, 1:24 a.m.