Triple
T22000813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Furey |
E543319
|
entity |
| Predicate | appointedToSenate |
P71782
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [George Furey, appointedToSenate, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedToSenate Context triple: [George Furey, appointedToSenate, 1999]
-
A.
numberAppointedBySenate
Indicates the number of individuals who were appointed to a position or role through the formal approval or decision of a senate.
-
B.
appointedIn
chosen
Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
-
C.
appointedAfter
Indicates that one entity was appointed to a position or role at a later time than another entity.
-
D.
succeededInOfficeAsSenatorBy
Indicates that one senator left office and was directly followed in that same senatorial position by another specific senator.
-
E.
representedInSenate
Indicates that an entity serves as a representative for another entity within a senate or upper legislative chamber.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276ae4e0819097bf1b978451f776 |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:20 p.m.