Triple
T1426182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubert H. Humphrey |
E30336
|
entity |
| Predicate | termStartAsSenatorFromMinnesota |
P25747
|
FINISHED |
| Object | 1949-01-03 |
—
|
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-01-03 | Statement: [Hubert H. Humphrey, termStartAsSenatorFromMinnesota, 1949-01-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsSenatorFromMinnesota Context triple: [Hubert H. Humphrey, termStartAsSenatorFromMinnesota, 1949-01-03]
-
A.
startTimeAsUnitedStatesSenator
chosen
Indicates the date and time at which an individual began serving in the role of United States Senator.
-
B.
startTimeAsUSCongressSeat
Indicates the date and time at which an individual officially begins serving in a specific seat in the U.S. Congress.
-
C.
termStartAsGovernor
Indicates the date or point in time when an individual begins their term serving in the role of governor.
-
D.
startTimeOfPoliticalCareer
Indicates the point in time when an individual’s political career officially began.
-
E.
inauguralHolderStartDate
Indicates the date on which the first person or entity to hold a position, title, or role officially began their tenure.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.