Triple
T37544280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryson DeChambeau |
E933413
|
entity |
| Predicate | teamInLIVGolf |
P188238
|
FINISHED |
| Object | Crushers GC |
—
|
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: Crushers GC | Statement: [Bryson DeChambeau, teamInLIVGolf, Crushers GC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamInLIVGolf Context triple: [Bryson DeChambeau, teamInLIVGolf, Crushers GC]
-
A.
RyderCupTeam
Indicates that one entity is a Ryder Cup team associated with or representing another entity (such as a country, region, or organization) in the Ryder Cup golf competition.
-
B.
playsForTitle
Indicates that an entity performs or competes on behalf of a team, organization, or group under a specific title or designation.
-
C.
leagueUsedBy
Indicates that a particular league is utilized, participated in, or otherwise employed by a given entity.
-
D.
RyderCupEquivalentTeam
Indicates that two golf teams are considered equivalent in the context of the Ryder Cup, typically for comparison, mapping, or alignment of team representations.
-
E.
menTeamPlaysIn
Indicates that a men's team participates or competes in a particular league, division, or competition.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.