Triple
T17685084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AP Top 25 Poll |
E440867
|
entity |
| Predicate | numberOfRankedTeams |
P39431
|
FINISHED |
| Object | 25 |
—
|
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: 25 | Statement: [AP Top 25 Poll, numberOfRankedTeams, 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRankedTeams Context triple: [AP Top 25 Poll, numberOfRankedTeams, 25]
-
A.
includesTopRankedTeams
Indicates that the referenced set, group, or collection contains one or more entities that are classified among the highest-ranked within a specified ranking system or category.
-
B.
numberOfRankedEntities
chosen
Indicates the total count of entities that have been assigned a rank within a given ranking or ordered set.
-
C.
qualifiedTeamsCount
Indicates the number of teams that have successfully met the criteria to qualify for a given stage, event, or competition.
-
D.
numberOfRankedPeople
Indicates the total count of people who have been assigned a rank within a given context or system.
-
E.
hadTeamsRankedIn
Indicates that an entity (such as a person, organization, or ranking body) assigned or held teams at specific positions within a ranking during a particular period or event.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704710488190826aaf0bdd4b2088 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:02 a.m.