Triple
T36667407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnoustie Golf Links |
E905303
|
entity |
| Predicate | hostedOpenInYear |
P16171
|
FINISHED |
| Object | 1931 |
—
|
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: 1931 | Statement: [Carnoustie Golf Links, hostedOpenInYear, 1931]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedOpenInYear Context triple: [Carnoustie Golf Links, hostedOpenInYear, 1931]
-
A.
hostedEventYear
chosen
Indicates the specific year in which an entity hosted a particular event.
-
B.
isOpenAllYear
Indicates that the subject remains available or operational throughout the entire year without seasonal closures.
-
C.
structureOpeningYear
Indicates the calendar year in which a structure was first opened for use or public access.
-
D.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
E.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c79c2fb0819097c2a5113f55e8fb |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.