Triple
T28714591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evan Lysacek |
E729923
|
entity |
| Predicate | trainedUnderCoach |
P7113
|
FINISHED |
| Object | Frank Carroll |
—
|
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: Frank Carroll | Statement: [Evan Lysacek, trainedUnderCoach, Frank Carroll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainedUnderCoach Context triple: [Evan Lysacek, trainedUnderCoach, Frank Carroll]
-
A.
beganUnderCoach
Indicates that one entity started its activity, career, or involvement while being coached or supervised by another entity.
-
B.
hasCoachedFor
Indicates that one entity has served in a coaching role for another entity, such as a team, organization, or individual.
-
C.
influencedByCoach
Indicates that an entity’s performance, behavior, or development is affected or shaped by the guidance or actions of a coach.
-
D.
workedUnderHeadCoach
chosen
Indicates that one person held a role or position under the authority or supervision of another person who was serving as the head coach.
-
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.
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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 5:50 a.m.