Triple
T33225928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A People’s Tragedy: The Russian Revolution 1891–1924 |
E850551
|
entity |
| Predicate | coversFigure |
P37409
|
FINISHED |
| Object | Vladimir Lenin |
—
|
NE NERFINISHED |
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: Vladimir Lenin | Statement: [A People’s Tragedy: The Russian Revolution 1891–1924, coversFigure, Vladimir Lenin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversFigure Context triple: [A People’s Tragedy: The Russian Revolution 1891–1924, coversFigure, Vladimir Lenin]
-
A.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
B.
cover
chosen
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
C.
coverPosition
Indicates that one entity occupies or shields a specific position or area, providing coverage for it.
-
D.
coverSymbol
Indicates that one symbol or notation is used as a cover or representative marker for another entity in a given context.
-
E.
coversTo
Indicates that one entity extends its coverage or protective scope to include another 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:30 a.m.