Triple
T19280252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushkin Street |
E482167
|
entity |
| Predicate | namedForPersonDeathYear |
P123910
|
FINISHED |
| Object | 1837 |
—
|
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: 1837 | Statement: [Pushkin Street, namedForPersonDeathYear, 1837]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForPersonDeathYear Context triple: [Pushkin Street, namedForPersonDeathYear, 1837]
-
A.
yearOfDeath
Indicates the specific year in which an entity (typically a person or organism) died.
-
B.
namedAfterDateOfDeath
chosen
Indicates that something is named after an entity specifically using the date on which that entity died.
-
C.
compilerDeathYearGregorian
Indicates the year, in the Gregorian calendar, in which the compiler of a work died.
-
D.
notableBearerDeathYear
Indicates the year in which a notable bearer of the referenced name, title, or role died.
-
E.
deathYearInferredFrom
Indicates that an entity’s year of death is not directly known but has been deduced based on other available information or evidence.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbfdfaf481909e0434f33053cc62 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.