Triple
T19936823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luhansk People’s Republic |
E479194
|
entity |
| Predicate | joinedRussiaClaimedDate |
P102136
|
FINISHED |
| Object | 2022-09-30 |
—
|
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: 2022-09-30 | Statement: [Luhansk People’s Republic, joinedRussiaClaimedDate, 2022-09-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedRussiaClaimedDate Context triple: [Luhansk People’s Republic, joinedRussiaClaimedDate, 2022-09-30]
-
A.
joinedSovietUnionAfter
Indicates that one entity became a member of or was incorporated into the Soviet Union after another specified time or event.
-
B.
joinedRussianEmpire
Indicates that an entity became part of, or was incorporated into, the Russian Empire.
-
C.
legalStatusClaimedByRussia
chosen
Indicates that Russia asserts a particular legal status or claim over the referenced entity or territory.
-
D.
rejoinedCountryYear
Indicates the year in which an entity re-entered or rejoined a particular country after having previously left or been separated from it.
-
E.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a17fb2c8190b3aaae88e741648a |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.