Triple
T26498254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond High School |
E669341
|
entity |
| Predicate | hasNotableCoachDepicted |
P54908
|
FINISHED |
| Object | Ken Carter |
—
|
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: Ken Carter | Statement: [Richmond High School, hasNotableCoachDepicted, Ken Carter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCoachDepicted Context triple: [Richmond High School, hasNotableCoachDepicted, Ken Carter]
-
A.
notableCoach
Indicates that one entity is a coach who is widely recognized or distinguished in relation to the other entity.
-
B.
notableCoachesInvolved
chosen
Indicates that certain coaches, recognized for their significance or prominence, were involved in relation to the subject entity.
-
C.
hasNotableAthleteTrained
Indicates that one entity (typically a coach, club, or institution) has trained a particular athlete who is considered notable or distinguished.
-
D.
notableAssistantCoaches
Indicates that the subject has assistant coaches who are particularly distinguished or noteworthy in their roles.
-
E.
notableCoachAlumnus
Indicates that a person is a notable former player or trainee of a particular coach.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 27, 2026, 1:10 a.m.