Triple
T18906842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas Supreme Court |
E462484
|
entity |
| Predicate | hasPositionsLabel |
P9248
|
FINISHED |
| Object | justices |
—
|
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: justices | Statement: [Kansas Supreme Court, hasPositionsLabel, justices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionsLabel Context triple: [Kansas Supreme Court, hasPositionsLabel, justices]
-
A.
hasPositionsFor
Indicates that one entity offers or contains available roles, jobs, or positions for another entity.
-
B.
hasLabel
chosen
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
-
C.
isLabeledOn
Indicates that a label, tag, or identifying text is physically or virtually attached to or displayed on an entity.
-
D.
hasAssociatedPosition
Indicates that one entity is linked to a specific role, job, or spatial/organizational position associated with it.
-
E.
recognizedPositions
Indicates that certain positions, roles, or locations have been formally identified, acknowledged, or accepted within a given context.
- 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_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.