Triple
T35027096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Skakel |
E1010368
|
entity |
| Predicate | appealFiled |
P89736
|
FINISHED |
| Object | Connecticut Supreme Court |
—
|
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: Connecticut Supreme Court | Statement: [Michael Skakel, appealFiled, Connecticut Supreme Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealFiled Context triple: [Michael Skakel, appealFiled, Connecticut Supreme Court]
-
A.
appeal
Indicates that one party formally requests a higher authority to review, reconsider, or overturn a prior decision, judgment, or outcome.
-
B.
appealStatus
Indicates the current state or outcome of an appeal within a review or decision process.
-
C.
legalActionFiled
chosen
Indicates that a formal legal proceeding or complaint has been officially initiated with the appropriate authority or court.
-
D.
filedAs
Indicates that one entity has been officially submitted or registered in a particular form, category, or designation as another entity.
-
E.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:01 p.m.