Triple
T13422604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Governor |
E313393
|
entity |
| Predicate | powersDefinedBy |
P8541
|
FINISHED |
| Object | state constitution |
—
|
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: state constitution | Statement: [Lieutenant Governor, powersDefinedBy, state constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powersDefinedBy Context triple: [Lieutenant Governor, powersDefinedBy, state constitution]
-
A.
powers
Indicates that one entity supplies or provides the energy, authority, or driving force that enables another entity to function or operate.
-
B.
intendedPowers
Indicates that one entity is meant or designed to have certain powers, authorities, or capabilities in relation to another entity or context.
-
C.
definesPowersOf
chosen
Indicates that one entity specifies or determines the scope, limits, or nature of the authority or powers held by another entity.
-
D.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
E.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaecf13748190ae40c7b95164f914 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:39 p.m.