Triple
T2012051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Open Championship |
E43708
|
entity |
| Predicate | firstPlayedYear |
P19145
|
FINISHED |
| Object | 1860 |
—
|
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: 1860 | Statement: [The Open Championship, firstPlayedYear, 1860]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPlayedYear Context triple: [The Open Championship, firstPlayedYear, 1860]
-
A.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
B.
firstYearPlayed
Indicates the year in which an entity (such as a person or team) first began participating in the specified activity or domain.
-
C.
firstSeriesYear
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
-
D.
firstRunningYear
chosen
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
E.
firstWinnerYear
Indicates the year in which an entity first won a particular competition, award, or title.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b2ed6c8190ad51f0af90db2a02 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.