Triple
T27061581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shea Daniels |
E685057
|
entity |
| Predicate | legalStatusDuringSeries |
P126617
|
FINISHED |
| Object | convict |
—
|
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: convict | Statement: [Shea Daniels, legalStatusDuringSeries, convict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusDuringSeries Context triple: [Shea Daniels, legalStatusDuringSeries, convict]
-
A.
legalStatusInSeries
chosen
Indicates the specific legal standing or role an entity holds within a particular series or grouped legal structure.
-
B.
legalStatusDuringEvent
Indicates the legal status or condition an entity holds specifically during the time period of a given event.
-
C.
statusAtStartOfSeries
Indicates the condition or state an entity has at the beginning of a specified series or sequence.
-
D.
legalStatusAfterEvent
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
-
E.
legalStatusAtIssue
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 27, 2026, 8:22 a.m.