Triple
T6610714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andriy Shevchenko |
E149228
|
entity |
| Predicate | startOfManagerialCareer |
P59499
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Andriy Shevchenko, startOfManagerialCareer, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfManagerialCareer Context triple: [Andriy Shevchenko, startOfManagerialCareer, 2016]
-
A.
managerialCareerStart
chosen
Indicates the point in time when an individual begins their professional role as a manager or coach.
-
B.
timeAsManagerStart
Indicates the point in time when an entity first began serving in a managerial role over another entity.
-
C.
startTimeOfProfessionalCareer
Indicates the point in time when an individual’s professional career formally begins.
-
D.
managerialCareerEnd
Indicates the point in time or event at which an individual's managerial career comes to an end.
-
E.
managerialRoleEnd
Indicates the point in time or event at which a person’s managerial role or position comes to an end.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.