Triple
T16686303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyron Garner |
E405469
|
entity |
| Predicate | decisionDateOfRelatedCase |
P2232
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Tyron Garner, decisionDateOfRelatedCase, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionDateOfRelatedCase Context triple: [Tyron Garner, decisionDateOfRelatedCase, 2003]
-
A.
decisionDate
chosen
Indicates the date on which a specific decision was formally made or finalized.
-
B.
notableCaseDate
Indicates the date on which a particular case or legal matter became notable or was formally recognized as significant.
-
C.
legalCaseHeParticipatedInDecidedBy
Indicates that a legal case in which he participated was decided or adjudicated by a specified authority or court.
-
D.
trialDate
Indicates the specific calendar date on which a legal trial or court proceeding is scheduled or took place.
-
E.
relatedCase
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea63b7081908a055036172f9683 |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.