Triple
T10631709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Brady |
E250471
|
entity |
| Predicate | chairmanshipStartTime |
P1814
|
FINISHED |
| Object | 2015-11-05 |
—
|
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: 2015-11-05 | Statement: [Kevin Brady, chairmanshipStartTime, 2015-11-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chairmanshipStartTime Context triple: [Kevin Brady, chairmanshipStartTime, 2015-11-05]
-
A.
currentChairStartDate
Indicates the date on which the person’s current term as chair officially began.
-
B.
officeHolderStartTime
chosen
Indicates the date and time at which an individual begins holding a particular office or position.
-
C.
chairmanshipRotates
Indicates that the role of chairperson is periodically transferred from one individual or entity to another according to a set rotation.
-
D.
lastOfficeHolderStartDate
Indicates the date on which the most recent person to hold a particular office or position began their term.
-
E.
timeInOfficeBeginsIn
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df94dc1c8190b6347eaf35a5acc2 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:01 p.m.