Triple
T14925122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Hay |
E371612
|
entity |
| Predicate | term start for United States Court of Claims |
P80322
|
FINISHED |
| Object | 1916 |
—
|
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: 1916 | Statement: [James Hay, term start for United States Court of Claims, 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: term start for United States Court of Claims Context triple: [James Hay, term start for United States Court of Claims, 1916]
-
A.
serviceOnCourtOfFederalClaimsStart
chosen
Indicates the date on which an entity’s service on the United States Court of Federal Claims begins.
-
B.
termStart (Sixth Circuit)
Indicates the date or point in time when a term or session of the Sixth Circuit officially begins.
-
C.
legalTermStart
Indicates that a specified legal term, period, or contractual timeframe begins at a particular point in time.
-
D.
termOfCourt
Indicates the specific judicial session or period during which a court is formally in operation for a case or legal matter.
-
E.
appointedToCourtOfFederalClaimsBy
Indicates that one entity formally selected and installed another entity as a judge on the United States Court of Federal Claims.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded633da0c8190b39f606212e48e71 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:35 a.m.