Triple
T30720782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia |
E782148
|
entity |
| Predicate | hasGovernorOffice |
P8673
|
FINISHED |
| Object | Governor of Georgia |
—
|
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: Governor of Georgia | Statement: [Georgia, hasGovernorOffice, Governor of Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernorOffice Context triple: [Georgia, hasGovernorOffice, Governor of Georgia]
-
A.
succeededInOfficeAsGovernorBy
Indicates that one individual’s term as governor ended and was directly followed by another individual’s term in the same office.
-
B.
hadGovernor
chosen
Indicates that an administrative region or political entity was governed by a specific person who held the office of governor.
-
C.
hasResidentGovernor
Indicates that a place or territory has an officially appointed governor who resides there and exercises governing authority over it.
-
D.
hasGubernatorialMember
Indicates that an entity has, as part of its composition or governance, a member who holds or has held the office of governor.
-
E.
hasGovernedState
Indicates that a person or governing body has exercised official governing authority over a particular state or political 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:36 p.m.