Triple
T34631698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Fadden |
E889306
|
entity |
| Predicate | servedAsTreasurerFrom |
P140344
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Arthur Fadden, servedAsTreasurerFrom, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsTreasurerFrom Context triple: [Arthur Fadden, servedAsTreasurerFrom, 1949]
-
A.
predecessorAsTreasurer
Indicates that one entity previously held the role of treasurer before another entity, establishing a predecessor relationship in that office.
-
B.
hasTreasurer
Indicates that one entity serves as the treasurer (i.e., the person or body responsible for managing funds) for another entity.
-
C.
termStartAsTreasurer
chosen
Indicates the point in time when an individual begins serving in the role of treasurer.
-
D.
succeededInOfficeAsSecretaryOfTheTreasury
Indicates that one person directly followed another in holding the position of Secretary of the Treasury.
-
E.
memberHeldOfficeFrom
Indicates that a member began holding a particular office or position starting from a specified date or time.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 1, 2026, 2:04 a.m.