Triple
T18906843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas Supreme Court |
E462484
|
entity |
| Predicate | hasChiefJudgeLabel |
P10517
|
FINISHED |
| Object | chief justice |
—
|
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: chief justice | Statement: [Kansas Supreme Court, hasChiefJudgeLabel, chief justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChiefJudgeLabel Context triple: [Kansas Supreme Court, hasChiefJudgeLabel, chief justice]
-
A.
hasChiefJudge
chosen
Indicates that an entity holds the role or position of chief judge for another entity (such as a court or judicial body).
-
B.
hasPrincipalJudge
Indicates that one entity serves as the main or presiding judge for another entity, such as a court or judicial body.
-
C.
judicialHead
Indicates that one entity serves as the chief or leading judicial authority over another entity, such as a court or legal body.
-
D.
hasSeniorJudge
Indicates that one entity is assigned or linked to another entity serving in the role of a senior judge.
-
E.
hasPresidentJudge
Indicates that a specified judicial body or court has a particular individual serving as its president judge (chief or presiding judge).
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52dcb948190a5b6a783512bf7d6 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.