Triple
T13781854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Open |
E331149
|
entity |
| Predicate | firstHeldAsScottishOpen |
P111443
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Scottish Open, firstHeldAsScottishOpen, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHeldAsScottishOpen Context triple: [Scottish Open, firstHeldAsScottishOpen, 1998]
-
A.
firstHeldAsSeparateTournament
Indicates that an event was initially conducted as an independent, standalone tournament rather than as part of another competition.
-
B.
firstHeldAsWorldChampionshipRound
Indicates the event or race at which a competition was first officially held as a round of the world championship.
-
C.
firstHeldAsCommonwealthGames
Indicates the event or location where something was initially hosted as part of the Commonwealth Games.
-
D.
OpenChampionshipWin
Indicates that an entity has achieved victory in an edition of the Open Championship (often known as The Open or British Open).
-
E.
firstHeldAsCombinedEvent
Indicates that an event was held for the first time as a combined or joint occurrence, rather than as separate events.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0247ccc881908dad7b547221f15d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.