Triple
T307203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Oregon |
E6328
|
entity |
| Predicate | hasGovernorTermLength |
P540
|
FINISHED |
| Object | 4 years |
—
|
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: 4 years | Statement: [Government of Oregon, hasGovernorTermLength, 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernorTermLength Context triple: [Government of Oregon, hasGovernorTermLength, 4 years]
-
A.
numberOfGovernors
Indicates the total count of governors associated with or governing a specified entity.
-
B.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
C.
termLimitDefinedBy
Indicates that the duration or number of terms for holding a position is specified or constrained by a particular rule, law, or authority.
-
D.
hasResidentGovernor
Indicates that a place or territory has an officially appointed governor who resides there and exercises governing authority over it.
-
E.
hasLieutenantGovernor
Indicates that one entity serves as the lieutenant governor of another entity (typically a state, province, or territory).
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93f38308190b4b480c951f1a1c3 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.