Triple
T34843859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEC Tournament MVP |
E1004412
|
entity |
| Predicate | awardedForPhase |
P19556
|
FINISHED |
| Object | conference tournament |
—
|
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: conference tournament | Statement: [SEC Tournament MVP, awardedForPhase, conference tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedForPhase Context triple: [SEC Tournament MVP, awardedForPhase, conference tournament]
-
A.
awardForPhase
chosen
Indicates that an award is given specifically in connection with, or as a result of, a particular phase of a process or project.
-
B.
awardedDuring
Indicates that an award or honor was given to an entity within a specified time period or event.
-
C.
awardedWhen
Indicates the time or condition under which an award or recognition is given to an entity.
-
D.
awardedSince
Indicates that an entity has been receiving a particular award continuously from a specified starting time onward.
-
E.
isAwardedWithin
Indicates that an award or recognition is granted to an entity within a specified context, scope, or time frame.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4 p.m.