Triple
T36917110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia vs Texas Tech |
E913072
|
entity |
| Predicate | headCoachTeam2 |
P33087
|
FINISHED |
| Object | Chris Beard |
—
|
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: Chris Beard | Statement: [Virginia vs Texas Tech, headCoachTeam2, Chris Beard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headCoachTeam2 Context triple: [Virginia vs Texas Tech, headCoachTeam2, Chris Beard]
-
A.
headCoachTeam
Indicates that a person serves as the head coach of a particular team.
-
B.
headCoachFullName
Indicates the full personal name of the individual who serves as head coach for a given team or organization.
-
C.
headCoachOfHomeTeam
Indicates that a person serves as the head coach of the designated home team in a sporting event or competition.
-
D.
headCoachFrom
Indicates that one entity serves as the head coach and originates from, or is affiliated with, the location or organization represented by the other entity.
-
E.
awayTeamHeadCoach
chosen
Indicates that the specified person serves as the head coach of the designated away team in a sporting event or competition.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.