Triple
T16601742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference USA football |
E403345
|
entity |
| Predicate | bowlSubdivisionStatus |
P123213
|
FINISHED |
| Object | FBS |
—
|
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: FBS | Statement: [Conference USA football, bowlSubdivisionStatus, FBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlSubdivisionStatus Context triple: [Conference USA football, bowlSubdivisionStatus, FBS]
-
A.
statusOfSubunit
Indicates the current condition, state, or operational situation of a component or subunit in relation to its larger whole.
-
B.
subdivisionStatus
chosen
Indicates the current state or phase of a subdivision process or classification for an entity.
-
C.
divisionStatus
Indicates the current operational or organizational state of a division within a larger entity.
-
D.
countrySubdivisionStatus
Indicates the administrative or political status assigned to a specific subdivision within a country (such as state, province, or territory).
-
E.
hasSubregionStatus
Indicates that one region holds an official or defined status as a subregion within a larger geographic or administrative area.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d764574819081366374ca0c9bea |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.