Triple
T23465919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Open Championship Trophy |
E569101
|
entity |
| Predicate | majorChampionshipStatus |
P43614
|
FINISHED |
| Object | one of the four men’s golf majors |
—
|
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: one of the four men’s golf majors | Statement: [U.S. Open Championship Trophy, majorChampionshipStatus, one of the four men’s golf majors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorChampionshipStatus Context triple: [U.S. Open Championship Trophy, majorChampionshipStatus, one of the four men’s golf majors]
-
A.
majorChampionship
Indicates that an entity has won or holds a significant, top-tier championship title in a competitive field.
-
B.
majorChampionshipSince
Indicates that an entity has won at least one major championship title starting from a specified time or year.
-
C.
championshipStatus
Indicates the competitive or title-holding state of an entity within a championship or league context.
-
D.
majorChampionshipWins
Indicates the number of major championship titles an entity has won.
-
E.
majorTournament
chosen
Indicates that an event is classified as a major, high-prestige tournament within its competitive domain.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6faaf8c8190b4fd191c54e1acea |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.