Triple
T24104334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Bowl |
E597177
|
entity |
| Predicate | typicalPlayersFrom |
P13494
|
FINISHED |
| Object | NCAA Division I FBS programs |
—
|
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: NCAA Division I FBS programs | Statement: [Senior Bowl, typicalPlayersFrom, NCAA Division I FBS programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlayersFrom Context triple: [Senior Bowl, typicalPlayersFrom, NCAA Division I FBS programs]
-
A.
featuresPlayersFrom
chosen
Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
-
B.
featuresPlayers
Indicates that something includes or showcases one or more players as part of its content or composition.
-
C.
featuresTopPlayersFrom
Indicates that something includes or showcases the most prominent or best-performing players from a specified source or group.
-
D.
recommendedPlayers
Indicates the suggested or optimal number of players that should participate in an activity or game.
-
E.
teamTypePlayedFor
Indicates the type or category of team (e.g., national, club, youth) that an entity has played for.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1399108190986f604468cd5858 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:01 p.m.