Triple
T13013183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lance Leipold |
E322473
|
entity |
| Predicate | hasCoachingExperienceAs |
P107825
|
FINISHED |
| Object | graduate assistant |
—
|
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: graduate assistant | Statement: [Lance Leipold, hasCoachingExperienceAs, graduate assistant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoachingExperienceAs Context triple: [Lance Leipold, hasCoachingExperienceAs, graduate assistant]
-
A.
hasCoachedFor
Indicates that one entity has served in a coaching role for another entity, such as a team, organization, or individual.
-
B.
hasCoachingStructure
Indicates that one entity provides an organized coaching framework, system, or arrangement for another entity.
-
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.
isActiveAsCoach
Indicates that an entity is currently functioning in the role of a coach within a given context or organization.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecbb8f4819094d55eb07cb5ad97 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e74283c819082e69ac3554fa7d8 |
completed | April 10, 2026, 10:49 p.m. |
Created at: April 9, 2026, 8:49 p.m.