Triple
T20289064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebecca Lynn Hammon |
E509967
|
entity |
| Predicate | startTimeAsAssistantCoachWithSanAntonioSpurs |
P79924
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Rebecca Lynn Hammon, startTimeAsAssistantCoachWithSanAntonioSpurs, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsAssistantCoachWithSanAntonioSpurs Context triple: [Rebecca Lynn Hammon, startTimeAsAssistantCoachWithSanAntonioSpurs, 2014]
-
A.
startTimeWithTeam
chosen
Indicates the time at which an activity, event, or engagement begins in association with a specific team.
-
B.
startTimeAsCaptain
Indicates the point in time when an entity first assumes the role or position of captain.
-
C.
firstSeasonInSanAntonio
Indicates the season in which an entity (such as a team or player) is in San Antonio for the first time.
-
D.
beganUnderCoach
Indicates that one entity started its activity, career, or involvement while being coached or supervised by another entity.
-
E.
coachedSeasonStart
Indicates that a person began serving as a coach for a team or individual at the start of a specific season.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67694d50881909d59c1037295c1d0 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:10 a.m.