Triple
T1188360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Open (golf) |
E25298
|
entity |
| Predicate | majorStatus |
P26153
|
FINISHED |
| Object | one of the four men's major golf championships |
—
|
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 major golf championships | Statement: [U.S. Open (golf), majorStatus, one of the four men's major golf championships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorStatus Context triple: [U.S. Open (golf), majorStatus, one of the four men's major golf championships]
-
A.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
B.
majorState
Indicates that a state holds significant power, influence, or importance relative to other states within a given system or context.
-
C.
majorPass
Indicates that an entity successfully completes or passes a significant or primary stage, requirement, or examination in relation to another entity or process.
-
D.
majorUse
Indicates that something serves as the primary or most significant use or application of an entity.
-
E.
majorCase
Indicates that a legal case is of primary importance or high significance within a given context.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:45 p.m.