Triple
T36917123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia vs Texas Tech |
E913072
|
entity |
| Predicate | notablePlayerTexasTech |
P205636
|
FINISHED |
| Object | Jarrett Culver |
E2204300
|
NE 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: Jarrett Culver | Statement: [Virginia vs Texas Tech, notablePlayerTexasTech, Jarrett Culver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerTexasTech Context triple: [Virginia vs Texas Tech, notablePlayerTexasTech, Jarrett Culver]
-
A.
notableBowlParticipant
Indicates that an entity has participated in a bowl game in a way considered notable or significant.
-
B.
notableUndraftedPlayer
Indicates that a player is recognized for significant achievements or impact despite not having been selected in a professional league draft.
-
C.
notablePlayerDallasStars
Indicates that a person is a notable or prominent player for the Dallas Stars hockey team.
-
D.
notablePlayer_FloridaState
Indicates that the person is a notable or distinguished player associated with the Florida State sports program.
-
E.
notableTeammate
Indicates that one entity has a teammate relationship with another entity who is particularly prominent, distinguished, or noteworthy.
- F. None of above. chosen
Provenance (5 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c29f6008190a49564e59360ca36 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.