Triple
T26204445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T Pebble Beach Pro-Am |
E655322
|
entity |
| Predicate | playedAtCourse |
P35416
|
FINISHED |
| Object | Pebble Beach Golf Links |
—
|
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: Pebble Beach Golf Links | Statement: [AT&T Pebble Beach Pro-Am, playedAtCourse, Pebble Beach Golf Links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedAtCourse Context triple: [AT&T Pebble Beach Pro-Am, playedAtCourse, Pebble Beach Golf Links]
-
A.
playedOnCourse
chosen
Indicates that an entity (typically a player or team) participated in a game, match, or round that took place on a specific course.
-
B.
playedAfter
Indicates that one event, performance, or action occurred later in time than another.
-
C.
hasBeenPlayedAt
Indicates that an entity (such as a song, track, or media item) has been performed or broadcast at a particular time, place, or event.
-
D.
playedAtLevel
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
-
E.
playedWhile
Indicates that one activity or event occurred concurrently with another, with the second serving as the temporal context during which the first was performed.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 8:50 p.m.