Triple
T37989896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gusztáv Sebes |
E947795
|
entity |
| Predicate | startTimeOfManagerialTenure |
P1814
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Gusztáv Sebes, startTimeOfManagerialTenure, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfManagerialTenure Context triple: [Gusztáv Sebes, startTimeOfManagerialTenure, 1949]
-
A.
notableManagerTenureStart
Indicates the date or point in time when a manager’s particularly significant or distinguished period of managing an entity began.
-
B.
tenureAsGeneralManagerStart
Indicates the date or time when an individual begins their tenure serving as a general manager.
-
C.
timeAsManagerStart
Indicates the point in time when an entity first began serving in a managerial role over another entity.
-
D.
officeHolderStartTime
chosen
Indicates the date and time at which an individual begins holding a particular office or position.
-
E.
significantOfficeHolderStartTime
Indicates the date and time at which an entity begins holding a significant office or position.
- 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_6a015ff02814819094806517fc4c69fa |
completed | May 11, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a0154ddd3c48190b85f9f48731cfd8f |
completed | May 11, 2026, 4:02 a.m. |
Created at: May 3, 2026, 4:20 p.m.