Triple
T2109041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Life of Klim Samgin |
E42461
|
entity |
| Predicate | settingPeriodStart |
P288
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [The Life of Klim Samgin, settingPeriodStart, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingPeriodStart Context triple: [The Life of Klim Samgin, settingPeriodStart, late 19th century]
-
A.
banPeriodStart
Indicates the date or time at which a ban or prohibition begins to take effect.
-
B.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
C.
settingStartYear
Indicates the year in which a particular setting, configuration, or condition first becomes effective or begins to apply.
-
D.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
E.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae1bacc8190beffc9d0470e9190 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.