Triple
T12914503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silent Cal |
E308940
|
entity |
| Predicate | hasAssociatedOfficeTermEnd |
P106986
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Silent Cal, hasAssociatedOfficeTermEnd, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedOfficeTermEnd Context triple: [Silent Cal, hasAssociatedOfficeTermEnd, 1929]
-
A.
hasAssociatedOffice
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
-
B.
combinedOfficeExistedUntil
Indicates that a merged or joint office or position remained in existence up to a specified end time or date.
-
C.
affiliationEndedWith
Indicates that a previously existing affiliation or association between entities has come to an end at a specific point in time or under certain conditions.
-
D.
firstOfficeholderEnd
Indicates the point in time or event at which the tenure of the first officeholder in a given position or role comes to an end.
-
E.
secondOfficeHolderEndDate
Indicates the date on which the second person holding a particular office or position ended their term.
- F. None of above. chosen
Provenance (4 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a0d6508190bca9668e9e06abfe |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:41 p.m.