Triple
T3807206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Michigan |
E93035
|
entity |
| Predicate | governorTermLimit |
P19684
|
FINISHED |
| Object | 2 consecutive terms |
—
|
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: 2 consecutive terms | Statement: [Government of Michigan, governorTermLimit, 2 consecutive terms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governorTermLimit Context triple: [Government of Michigan, governorTermLimit, 2 consecutive terms]
-
A.
limitedReelectionOfGovernor
Indicates that the governor’s ability to be reelected is restricted, such as by term limits or a cap on consecutive terms.
-
B.
termLimitDefinedBy
Indicates that the duration or number of terms for holding a position is specified or constrained by a particular rule, law, or authority.
-
C.
servedAsGovernorUntil
Indicates that an entity held the position of governor up to a specified end date or time.
-
D.
maximumNumberOfTermsForGovernor
chosen
Indicates the highest number of terms that a governor is allowed to serve in office.
-
E.
electsTermLength
Indicates the length of time for which an entity is elected to hold a particular position or office.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.