Triple
T24913474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Football Playoff Selection Committee |
E623909
|
entity |
| Predicate | selectsForRound |
P66415
|
FINISHED |
| Object | national semifinals |
—
|
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: national semifinals | Statement: [College Football Playoff Selection Committee, selectsForRound, national semifinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectsForRound Context triple: [College Football Playoff Selection Committee, selectsForRound, national semifinals]
-
A.
selectsFor
chosen
Indicates that one entity chooses or designates another entity as the preferred or targeted option from a set of possible candidates.
-
B.
selectionRitual
Indicates a process or ceremony through which one or more entities are chosen from a set of candidates.
-
C.
includedRound
Indicates that a particular round is part of, or contained within, a larger set, sequence, or event of rounds.
-
D.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
E.
draftRound
Indicates the specific round in which an entity was selected during a drafting or selection process.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:28 a.m.