Triple
T97781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hal Steinbrenner |
E1969
|
entity |
| Predicate | startTimeOfRole |
P1814
|
FINISHED |
| Object | became managing general partner of the New York Yankees in 2008 |
—
|
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: became managing general partner of the New York Yankees in 2008 | Statement: [Hal Steinbrenner, startTimeOfRole, became managing general partner of the New York Yankees in 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfRole Context triple: [Hal Steinbrenner, startTimeOfRole, became managing general partner of the New York Yankees in 2008]
-
A.
officeHolderStartTime
chosen
Indicates the date and time at which an individual begins holding a particular office or position.
-
B.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
C.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
D.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
E.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebe7b1c8190a6bfbf31dc7c7f07 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.