Triple
T21567607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шанхайская пятёрка |
E532201
|
entity |
| Predicate | годПреобразования |
P10480
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Шанхайская пятёрка, годПреобразования, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: годПреобразования Context triple: [Шанхайская пятёрка, годПреобразования, 2001]
-
A.
eraOfConversion
Indicates the specific historical period or era during which the conversion event or change took place.
-
B.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
C.
dateOfConversion
chosen
Indicates the specific date on which an entity changed status, form, or affiliation (e.g., religious, legal, or organizational conversion).
-
D.
convertedIn
Indicates that one entity has been transformed, changed, or translated into another form, state, or representation within a specified context.
-
E.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9c9f264819085b4807923860793 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.