Triple
T12914502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silent Cal |
E308940
|
entity |
| Predicate | hasAssociatedOfficeTermStart |
P38523
|
FINISHED |
| Object | 1923 |
—
|
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: 1923 | Statement: [Silent Cal, hasAssociatedOfficeTermStart, 1923]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedOfficeTermStart Context triple: [Silent Cal, hasAssociatedOfficeTermStart, 1923]
-
A.
hasAssociatedOffice
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
-
B.
firstOfficeHolderStart
chosen
Indicates the date or time when the first person to hold a particular office or position began their term.
-
C.
hasSupportingOffice
Indicates that an entity is associated with or served by a particular office that provides support or administrative services to it.
-
D.
hasProperOffice
Indicates that an entity maintains an officially designated, appropriate office or place of business.
-
E.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
- 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_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. |
Created at: April 9, 2026, 5:41 p.m.