Triple
T27283201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sporting News College Football Player of the Year |
E688392
|
entity |
| Predicate | hasTypeOfSelection |
P74335
|
FINISHED |
| Object | media-selected award |
—
|
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: media-selected award | Statement: [Sporting News College Football Player of the Year, hasTypeOfSelection, media-selected award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfSelection Context triple: [Sporting News College Football Player of the Year, hasTypeOfSelection, media-selected award]
-
A.
typeOfSelection
chosen
Indicates the specific kind or category of selection being made in a given context.
-
B.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
C.
hasSelectionSize
Indicates that an entity has a specific size or extent associated with a chosen portion or selection of it.
-
D.
hasSelectionUnit
Indicates that an entity is associated with a specific unit or mechanism used to make a selection among available options.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 27, 2026, 11:09 a.m.