Triple
T31204851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal and Ancient Golf Club of St Andrews |
E795573
|
entity |
| Predicate | spunOffOrganizationIn |
P171358
|
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, spunOffOrganizationIn, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spunOffOrganizationIn Context triple: [Royal and Ancient Golf Club of St Andrews, spunOffOrganizationIn, 2004]
-
A.
spinoffMemberOf
Indicates that one entity originated as a spinoff from, and is organizationally or historically derived from, another entity.
-
B.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
C.
associatedCompanyHasSpinOff
Indicates that a company is related to another company that has been created as its spin-off.
-
D.
spinoffCreatorOf
Indicates that one entity created or developed a spinoff derived from another entity.
-
E.
spinoffRelation
Indicates a relationship where one entity originates as a derivative, offshoot, or spin-off from another entity.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:09 p.m.