Triple
T37989897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gusztáv Sebes |
E947795
|
entity |
| Predicate | endTimeOfManagerialTenure |
P4346
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [Gusztáv Sebes, endTimeOfManagerialTenure, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeOfManagerialTenure Context triple: [Gusztáv Sebes, endTimeOfManagerialTenure, 1956]
-
A.
notableManagerTenureStart
Indicates the date or point in time when a manager’s particularly significant or distinguished period of managing an entity began.
-
B.
RoyalsManagerTenureEnd
Indicates the time or event at which an individual's tenure as manager of the Kansas City Royals ends.
-
C.
tenureAsGeneralManagerEnd
Indicates the point in time when an entity’s tenure or service as a general manager comes to an end.
-
D.
endCoachTenure
Indicates that a coach’s period of service or employment with a team or organization has concluded.
-
E.
officeholderEndTime
chosen
Indicates the time or date at which a person’s term in a particular office 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:20 p.m.