Triple
T32183294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary of Kentucky |
E822039
|
entity |
| Predicate | hasTrialFunction |
P198629
|
FINISHED |
| Object | fact-finding in legal disputes |
—
|
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: fact-finding in legal disputes | Statement: [Judiciary of Kentucky, hasTrialFunction, fact-finding in legal disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrialFunction Context triple: [Judiciary of Kentucky, hasTrialFunction, fact-finding in legal disputes]
-
A.
hasTrial
Indicates that an entity is associated with a specific trial, such as a legal proceeding, clinical study, or experimental test.
-
B.
hasTrialBy
Indicates that a legal case, dispute, or matter is adjudicated or decided through a specified type of trial or judicial proceeding.
-
C.
hasTrialLevel
Indicates a relationship where an entity is associated with a specific stage or level within a trial or experimental process.
-
D.
hasFirstTrial
Indicates that an entity is associated with its initial or earliest trial, test, or legal proceeding.
-
E.
onTrialFor
Indicates that a person is currently being legally prosecuted or judged in court for a specific alleged offense or charge.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_69fef8c2cdd881908c6f44e4dfa5ffd0 |
completed | May 9, 2026, 9:05 a.m. |
Created at: May 1, 2026, 12:34 a.m.