Triple
T24833047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sprint Cup |
E621390
|
entity |
| Predicate | titleAwardedFor |
P107
|
FINISHED |
| Object | performance in designated sprint events |
—
|
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: performance in designated sprint events | Statement: [Sprint Cup, titleAwardedFor, performance in designated sprint events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleAwardedFor Context triple: [Sprint Cup, titleAwardedFor, performance in designated sprint events]
-
A.
holderAwardedFor
Indicates that an award holder received the award specifically in recognition of, or as a result of, a particular work, achievement, or contribution.
-
B.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
C.
recipientOfAward
Indicates that an entity has received or been granted a particular award.
-
D.
awardConferred
Indicates that an award or honor has been formally granted by one entity to another.
-
E.
awardFor
chosen
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 5:16 a.m.