Triple
T22836436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Young |
E565959
|
entity |
| Predicate | helpedLeadTeamTo |
P40241
|
FINISHED |
| Object | NCAA Final Four appearances |
—
|
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: NCAA Final Four appearances | Statement: [Michael Young, helpedLeadTeamTo, NCAA Final Four appearances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedLeadTeamTo Context triple: [Michael Young, helpedLeadTeamTo, NCAA Final Four appearances]
-
A.
helpedTeamTo
Indicates that one entity provided assistance or support to a team in achieving a task, goal, or outcome.
-
B.
helpedTransformTeam
Indicates that one entity played a significant role in changing or improving the performance, dynamics, or structure of a team.
-
C.
helpsLead
chosen
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
-
D.
ledTeamTo
Indicates that one entity acted as a leader or guiding force that directed a team toward achieving a particular goal, outcome, or success.
-
E.
teamLead
Indicates that one entity serves as the leader or primary coordinator of a team that includes the other entity.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2f09608190bc8e465e53b39e2e |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.