Triple
T33703530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Johnson |
E863522
|
entity |
| Predicate | collegeTeamCoachedLevel |
P26832
|
FINISHED |
| Object | NCAA Division I FBS |
—
|
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: NCAA Division I FBS | Statement: [Paul Johnson, collegeTeamCoachedLevel, NCAA Division I FBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collegeTeamCoachedLevel Context triple: [Paul Johnson, collegeTeamCoachedLevel, NCAA Division I FBS]
-
A.
collegeTeamCoached
Indicates that a person has served as a coach for a particular college sports team.
-
B.
collegeTeamCoach
Indicates that one entity serves as the coach of a college sports team represented by the other entity.
-
C.
playedForCollegeCoach
Indicates that an athlete was coached by a specific college coach while playing for that coach’s team.
-
D.
coachesLevel
chosen
Indicates the level or tier at which one entity coaches another, such as their rank, division, or proficiency category in a coaching context.
-
E.
teamCoachedFrom
Indicates that a coaching relationship exists where a coach is responsible for training or managing a team originating from a specific organization, location, or context.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 1:43 a.m.