Triple
T4739968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dick Howser |
E105213
|
entity |
| Predicate | leftManagerialPost |
P53082
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Dick Howser, leftManagerialPost, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftManagerialPost Context triple: [Dick Howser, leftManagerialPost, 1986]
-
A.
manager
Indicates that one entity holds a supervisory or administrative role with authority and responsibility over another entity.
-
B.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
C.
leftOffice
Indicates that an entity ceased holding or performing the duties of a particular office or position.
-
D.
executiveFor
Indicates that one entity serves in an executive role (such as CEO, president, or similar leadership position) for another entity, typically an organization or company.
-
E.
managerialRoleEnd
chosen
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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6486f8608190908e43b777810c44 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.