Triple
T8540274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonny Vaccaro |
E202176
|
entity |
| Predicate | laterCareerFocus |
P19158
|
FINISHED |
| Object | challenging NCAA amateurism rules |
—
|
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: challenging NCAA amateurism rules | Statement: [Sonny Vaccaro, laterCareerFocus, challenging NCAA amateurism rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCareerFocus Context triple: [Sonny Vaccaro, laterCareerFocus, challenging NCAA amateurism rules]
-
A.
laterCareer
chosen
Indicates that the associated information or events pertain to a later stage or phase in an entity’s professional life or career trajectory.
-
B.
managedCareerOf
Indicates that one entity was responsible for overseeing, directing, or handling the professional career of another entity.
-
C.
targetCareer
Indicates that one entity is the intended or pursued career or professional goal of another entity.
-
D.
plannedCareer
Indicates that an individual has chosen and intends to pursue a specific career path.
-
E.
careerField
Indicates the professional domain or occupational area in which an entity works or specializes.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6dfb2bc8190a41e32eca3c824c2 |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.