Triple
T26888872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Washington Bryant |
E677117
|
entity |
| Predicate | hasCoachedIn |
P197158
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Joseph Washington Bryant, hasCoachedIn, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoachedIn Context triple: [Joseph Washington Bryant, hasCoachedIn, United States]
-
A.
hasCoachedFor
Indicates that one entity has served in a coaching role for another entity, such as a team, organization, or individual.
-
B.
hasCoachingExperienceAs
Indicates that an entity has experience providing coaching in a specified role or capacity.
-
C.
hasCoachedDiscipline
Indicates that a person has coached or provided training in a particular discipline, field, or area of expertise.
-
D.
hasCoachedCompetition
Indicates that one entity has served as a coach for another entity in the context of a specific competition or contest.
-
E.
coachedAlongside
Indicates that two or more individuals served as coaches at the same time, typically for the same team, organization, or event.
- F. None of above. chosen
Provenance (4 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: April 27, 2026, 5:43 a.m.