Triple
T2446087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I Outdoor Track and Field Championships |
E53596
|
entity |
| Predicate | includesEventCategory |
P15481
|
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: [NCAA Division I Outdoor Track and Field Championships, includesEventCategory, sprints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEventCategory Context triple: [NCAA Division I Outdoor Track and Field Championships, includesEventCategory, sprints]
-
A.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
B.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
C.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
-
D.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
E.
isOneOfMajorCategories
Indicates that an entity belongs to a specified set of primary or top-level categories within a classification.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.