Triple
T16742664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Legislative Research Commission |
E406870
|
entity |
| Predicate | hasPrimaryClient |
P734
|
FINISHED |
| Object | members of the Kentucky House of Representatives |
—
|
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: members of the Kentucky House of Representatives | Statement: [Kentucky Legislative Research Commission, hasPrimaryClient, members of the Kentucky House of Representatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryClient Context triple: [Kentucky Legislative Research Commission, hasPrimaryClient, members of the Kentucky House of Representatives]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
hasClient
chosen
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
C.
hasPrimaryAccessType
Indicates that an entity is associated with its main or default mode or category of access.
-
D.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
-
E.
hasPrimaryCode
Indicates that an entity is associated with its main or most important identifying code among potentially multiple codes.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3f49808190b543d8da34031f3d |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.