Triple
T30938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I FCS |
E617
|
entity |
| Predicate | tierLevel |
P1906
|
FINISHED |
| Object | second tier of Division I football |
—
|
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: second tier of Division I football | Statement: [NCAA Division I FCS, tierLevel, second tier of Division I football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierLevel Context triple: [NCAA Division I FCS, tierLevel, second tier of Division I football]
-
A.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
B.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
C.
athleticAssociationTier
chosen
Indicates the competitive level or division within an athletic association to which an entity (such as a team or institution) belongs.
-
D.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
-
E.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490d80a0819083bf604c1229e903 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486eb01881909241540dda28e1ff |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.