Triple
T28983047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montana Constitution |
E734602
|
entity |
| Predicate | separatesPowerInto |
P142883
|
FINISHED |
| Object | legislative branch |
—
|
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: legislative branch | Statement: [Montana Constitution, separatesPowerInto, legislative branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesPowerInto Context triple: [Montana Constitution, separatesPowerInto, legislative branch]
-
A.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
-
B.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
C.
powerDistribution
Indicates how authority, control, or influence is allocated and shared among entities within a system or relationship.
-
D.
dividedPowersBetween
chosen
Indicates that some form of authority, control, or responsibility is distributed or shared between two or more entities rather than held by a single one.
-
E.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 9:12 a.m.