Triple
T30436386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fatherland – All Russia |
E774321
|
entity |
| Predicate | mergerDateApprox |
P92542
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Fatherland – All Russia, mergerDateApprox, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerDateApprox Context triple: [Fatherland – All Russia, mergerDateApprox, early 2000s]
-
A.
mergerYear
Indicates the year in which two or more entities formally merged into a single entity.
-
B.
timeOfMergerOrAcquisition
chosen
Indicates the specific point in time when a merger or acquisition event occurs between entities.
-
C.
mergerPeriod
Indicates the time span during which two or more entities are in the process of merging into a single combined entity.
-
D.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
E.
mergerAnnounced
Indicates that an official announcement has been made that two or more entities intend to merge into a single combined entity.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68694ff888190b85abd31df01a71c |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:07 p.m.