Triple
T21981967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Most Valuable Player Award |
E542863
|
entity |
| Predicate | isGivenFor |
P12882
|
FINISHED |
| Object | most outstanding performance over a season |
—
|
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: most outstanding performance over a season | Statement: [Most Valuable Player Award, isGivenFor, most outstanding performance over a season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGivenFor Context triple: [Most Valuable Player Award, isGivenFor, most outstanding performance over a season]
-
A.
givenFor
chosen
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
-
B.
isGivenBy
Indicates that something (such as an item, value, or information) is provided or granted by a particular source or giver.
-
C.
isGivenAt
Indicates that an event, service, or item is provided or occurs at a specific time or place.
-
D.
hasGiven
Indicates that one entity has transferred or presented something to another entity.
-
E.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248de3688190a8d24cc8458851f2 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:04 p.m.