Triple
T32840723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucas Glover |
E839959
|
entity |
| Predicate | hasNotableVictory |
P56419
|
FINISHED |
| Object | 2009 U.S. Open at Bethpage Black |
—
|
NE NERFINISHED |
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: 2009 U.S. Open at Bethpage Black | Statement: [Lucas Glover, hasNotableVictory, 2009 U.S. Open at Bethpage Black]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVictory Context triple: [Lucas Glover, hasNotableVictory, 2009 U.S. Open at Bethpage Black]
-
A.
hasNotableTeamSuccess
Indicates that an entity has achieved significant or distinguished success as part of a team.
-
B.
hasNotableSuccessIn
Indicates that an entity has achieved significant or widely recognized success in a particular field, activity, or domain.
-
C.
notableWin
chosen
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
D.
hasNotableScore
Indicates that an entity is associated with a score or rating considered significant or noteworthy in its context.
-
E.
hasNotableHit
Indicates that an entity is associated with a particularly successful, famous, or widely recognized work, performance, or achievement.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a01531add1c8190b51add7bb046e2cb |
completed | May 11, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_6a014fef3d8c81909b509d51d0c4cdc7 |
completed | May 11, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:16 a.m.