Triple
T21822060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCLA Bruins men's volleyball |
E538750
|
entity |
| Predicate | formerHeadCoachTenure |
P90754
|
FINISHED |
| Object | 1963–2012 |
—
|
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: 1963–2012 | Statement: [UCLA Bruins men's volleyball, formerHeadCoachTenure, 1963–2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerHeadCoachTenure Context triple: [UCLA Bruins men's volleyball, formerHeadCoachTenure, 1963–2012]
-
A.
headCoachTenure
Indicates the duration or period during which a specific individual serves as the head coach of a team or organization.
-
B.
headCoachPreviousTenure
chosen
Indicates that a person served as the head coach of a team or organization during a prior period before the current tenure.
-
C.
hiredAsHeadCoachYear
Indicates the year in which an individual was hired to serve as the head coach of a team or organization.
-
D.
returnedAsHeadCoach
Indicates that an individual resumed a previous role as head coach of a team or organization after a period of absence.
-
E.
servedAsInterimHeadCoachYear
Indicates that an entity held the position of interim head coach for another entity during a specified year.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0912e432481909045d00a61daa767 |
completed | April 28, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.