Triple
T31204849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal and Ancient Golf Club of St Andrews |
E795573
|
entity |
| Predicate | governanceRoleEndedIn |
P86224
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Royal and Ancient Golf Club of St Andrews, governanceRoleEndedIn, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governanceRoleEndedIn Context triple: [Royal and Ancient Golf Club of St Andrews, governanceRoleEndedIn, 2004]
-
A.
temporalAuthorityEndedBy
Indicates that a period of temporal authority or secular power held by one entity comes to an end as a result of an action or event caused by another entity.
-
B.
governedPeriodEnd
Indicates the point in time at which a governing authority’s control or jurisdiction over something comes to an end.
-
C.
endTimeOfRole
chosen
Indicates the point in time at which a particular role or position held by an entity concludes.
-
D.
secondOfficeHolderEndDate
Indicates the date on which the second person holding a particular office or position ended their term.
-
E.
thirdOfficeHolderEndDate
Indicates the date on which the third person to hold a particular office or position ended their term.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: April 29, 2026, 9:09 p.m.