Triple
T16962103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana judicial discipline |
E411453
|
entity |
| Predicate | includesOutcome |
P1393
|
FINISHED |
| Object | publication of certain disciplinary decisions |
—
|
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: publication of certain disciplinary decisions | Statement: [Indiana judicial discipline, includesOutcome, publication of certain disciplinary decisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOutcome Context triple: [Indiana judicial discipline, includesOutcome, publication of certain disciplinary decisions]
-
A.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
C.
includesResponse
Indicates that one entity contains, incorporates, or encompasses another entity as a response or reply.
-
D.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
includesFinal
Indicates that one entity contains or encompasses another entity as its concluding or last part.
- 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.