Triple
T32183276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary of Kentucky |
E822039
|
entity |
| Predicate | hasUnifiedSystem |
P127612
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Judiciary of Kentucky, hasUnifiedSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnifiedSystem Context triple: [Judiciary of Kentucky, hasUnifiedSystem, true]
-
A.
isUnifiedSystem
chosen
Indicates that multiple components or elements function together as a single, coherent, integrated system.
-
B.
hasUnifiedCommand
Indicates that multiple entities operate under a single, centralized authority or leadership structure for coordinated control.
-
C.
hasHybridSystem
Indicates that an entity is equipped with or incorporates a hybrid system, typically combining two or more different technologies or power sources.
-
D.
hasIntegratedUnit
Indicates that one entity includes another entity as a built-in or internally combined component or unit.
-
E.
isUnifiedCommand
Indicates that multiple entities operate under a single, integrated command structure or authority.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 12:34 a.m.