Triple
T20222090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Cavaliers women's track and field |
E495280
|
entity |
| Predicate | governsEvents |
P99378
|
FINISHED |
| Object | sprints |
—
|
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: sprints | Statement: [Virginia Cavaliers women's track and field, governsEvents, sprints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsEvents Context triple: [Virginia Cavaliers women's track and field, governsEvents, sprints]
-
A.
regulatesEvent
Indicates that one entity controls, influences, or modulates the occurrence, timing, or intensity of an event.
-
B.
governingBodyEvents
chosen
Indicates that a governing body organizes, oversees, or is formally associated with specific events.
-
C.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
D.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
E.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd729548190942bcf842f03c4cd |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.