Triple
T27693294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgy Yartsev |
E698213
|
entity |
| Predicate | workPeriodAsManager |
P70411
|
FINISHED |
| Object | 1980s–2000s |
—
|
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: 1980s–2000s | Statement: [Georgy Yartsev, workPeriodAsManager, 1980s–2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPeriodAsManager Context triple: [Georgy Yartsev, workPeriodAsManager, 1980s–2000s]
-
A.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
-
C.
workSettingPeriod
Indicates the time period during which a particular work setting or employment context is in effect.
-
D.
timeAsManagerStart
Indicates the point in time when an entity first began serving in a managerial role over another entity.
-
E.
activeAsManagerDuring
chosen
Indicates that an entity holds and performs the role of manager for another entity throughout a specified time period.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 2:52 p.m.