Triple
T26573298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyson Timbs |
E666882
|
entity |
| Predicate | stateOfLegalCase |
P176278
|
FINISHED |
| Object | Indiana |
—
|
NE NERFINISHED |
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: Indiana | Statement: [Tyson Timbs, stateOfLegalCase, Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfLegalCase Context triple: [Tyson Timbs, stateOfLegalCase, Indiana]
-
A.
statusInLegalSystem
Indicates the current standing or condition of an entity within a legal or judicial framework (e.g., pending, active, resolved, or appealed).
-
B.
courtStatus
Indicates the current legal or procedural state of a case or matter within a court system.
-
C.
stateOfLaw
Indicates that a specified legal condition, rule, or status is currently in force or applicable within a given jurisdiction or context.
-
D.
judicialStatus
Indicates the legal or court-related condition or standing of an entity within a judicial process (e.g., pending, decided, appealed).
-
E.
legalStatusOfProceedings
Indicates the current legal standing or condition of a set of legal proceedings within a judicial or administrative process.
- F. None of above. chosen
Provenance (4 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 27, 2026, 1:59 a.m.