Triple
T7466028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas legislative districts |
E176374
|
entity |
| Predicate | languageOfOfficialDescriptions |
P236
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Kansas legislative districts, languageOfOfficialDescriptions, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfOfficialDescriptions Context triple: [Kansas legislative districts, languageOfOfficialDescriptions, English]
-
A.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
B.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
C.
languageOfOfficialLists
Indicates the language in which official lists, records, or registries are formally maintained or published.
-
D.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
E.
officialLanguage
chosen
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3f412908190ac910ecae682d6f6 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:40 p.m.