Triple
T7549925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beloselsky-Belozersky family |
E178503
|
entity |
| Predicate | fateAfter1917 |
P59892
|
FINISHED |
| Object | loss of estates |
—
|
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: loss of estates | Statement: [Beloselsky-Belozersky family, fateAfter1917, loss of estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateAfter1917 Context triple: [Beloselsky-Belozersky family, fateAfter1917, loss of estates]
-
A.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
C.
historicalFate
Indicates that two entities share a common or interconnected outcome, destiny, or consequence within a historical context.
-
D.
statusAfter1917
chosen
Indicates the condition or state of an entity as it existed after the year 1917, typically in contrast to its prior status.
-
E.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b35ba481908e1e5bbf329daa33 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.