Triple
T24144071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Moffit |
E598324
|
entity |
| Predicate | spouseFormerPosition |
P123121
|
FINISHED |
| Object | Governor of Rhode Island |
—
|
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 Rhode Island | Statement: [Andrew Moffit, spouseFormerPosition, Governor of Rhode Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseFormerPosition Context triple: [Andrew Moffit, spouseFormerPosition, Governor of Rhode Island]
-
A.
spouseOfFormer
chosen
Indicates that one entity is the spouse of another entity who is a former holder of some role, status, or position.
-
B.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
-
C.
spouseLaterOffice
Indicates that one person’s spouse held a particular office or position at a later time than the person in question.
-
D.
spouseServedUnder
Indicates that one person’s spouse held a subordinate or reporting position under the authority, command, or supervision of another person.
-
E.
spouseDiplomaticRole
Indicates that one person is the spouse of another person who holds or held a diplomatic position or role.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e008efbc8190ac6c12d3ba5dd5d8 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:29 p.m.