Triple
T16962097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana judicial discipline |
E411453
|
entity |
| Predicate | proceduresSetBy |
P108768
|
FINISHED |
| Object | Indiana Supreme Court rules |
—
|
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: Indiana Supreme Court rules | Statement: [Indiana judicial discipline, proceduresSetBy, Indiana Supreme Court rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduresSetBy Context triple: [Indiana judicial discipline, proceduresSetBy, Indiana Supreme Court rules]
-
A.
proceduresDefinedBy
chosen
Indicates that certain procedures are specified, established, or authored by a particular entity.
-
B.
proceduresVaryBy
Indicates that the procedures or methods used differ depending on a specified factor, context, or category.
-
C.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
D.
adoptedRulesOfProcedureOn
Indicates that an entity formally established or approved rules of procedure on a specific date or occasion.
-
E.
typeOfProcedureHandled
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d021c5508190b6e3106554c07a9c |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.