Triple
T32952983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bennett Champ Clark |
E843010
|
entity |
| Predicate | startTime (judicial service) |
P20218
|
FINISHED |
| Object | 1945-03-30 |
—
|
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: 1945-03-30 | Statement: [Bennett Champ Clark, startTime (judicial service), 1945-03-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTime (judicial service) Context triple: [Bennett Champ Clark, startTime (judicial service), 1945-03-30]
-
A.
startTime (Chief Judge SDNY)
Indicates the specific time at which the tenure or role of the Chief Judge of the Southern District of New York begins.
-
B.
startTime (SDNY judgeship)
Indicates the date and time at which an individual’s service in the SDNY judgeship role begins.
-
C.
startTime (as Attorney General)
Indicates the date and time at which an individual began serving in the role of Attorney General.
-
D.
startTimeAsCircuitJudge
chosen
Indicates the point in time at which an individual begins serving in the role of a circuit judge.
-
E.
startTimeAsAssistantAttorneyGeneral
Indicates the point in time when an individual began serving in the role of Assistant Attorney General.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 1, 2026, 1:21 a.m.