Triple
T37523372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC Player of the Year |
E932839
|
entity |
| Predicate | higherLevelAward |
P1463
|
FINISHED |
| Object | NFL Most Valuable Player Award |
—
|
NE NERFINISHED |
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: NFL Most Valuable Player Award | Statement: [NFC Player of the Year, higherLevelAward, NFL Most Valuable Player Award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherLevelAward Context triple: [NFC Player of the Year, higherLevelAward, NFL Most Valuable Player Award]
-
A.
higherAward
chosen
Indicates that one entity has received an award that is of greater prestige, rank, or value than the award received by another entity.
-
B.
hasAwardLevel
Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
-
C.
isMajorAwardFor
Indicates that an award is a primary or highly prestigious recognition given specifically for a particular work, achievement, or contribution.
-
D.
holderAward
Indicates that an entity has received, possesses, or is the recipient of a particular award.
-
E.
hasLowerRankAward
Indicates that one award has a lower rank or level of distinction compared to another award.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:17 p.m.