Triple
T29649063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenin in October |
E756083
|
entity |
| Predicate | hasHistoricalFigureCharacter |
P137721
|
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: [Lenin in October, hasHistoricalFigureCharacter, Vladimir Lenin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalFigureCharacter Context triple: [Lenin in October, hasHistoricalFigureCharacter, Vladimir Lenin]
-
A.
basedOnHistoricalFigure
chosen
Indicates that something is derived from, inspired by, or modeled after a real historical person.
-
B.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
C.
sameHistoricalFigureAs
Indicates that two entities refer to the same historical person, treating them as different representations or records of one individual.
-
D.
favoriteHistoricalFigure
Indicates that one entity is the historical person whom another entity likes or admires the most.
-
E.
addressesHistoricalFigure
Indicates that one entity directly speaks or writes to a person recognized as a historical figure.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 6:51 p.m.