Triple
T20173364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson State Tigers football |
E492024
|
entity |
| Predicate | marchingBandReputation |
P40946
|
FINISHED |
| Object | nationally recognized HBCU marching band |
—
|
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: nationally recognized HBCU marching band | Statement: [Jackson State Tigers football, marchingBandReputation, nationally recognized HBCU marching band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marchingBandReputation Context triple: [Jackson State Tigers football, marchingBandReputation, nationally recognized HBCU marching band]
-
A.
featuresMarchingBands
chosen
Indicates that something includes or presents marching bands as part of its content or composition.
-
B.
choirReputation
Indicates the perceived quality or standing of a choir based on others’ opinions or evaluations.
-
C.
regimentalBand
Indicates that an entity serves as the official military band associated with a particular regiment.
-
D.
hasRoleInBand
Indicates that an entity holds a specific role or position within a band.
-
E.
militaryReputation
Indicates the perceived standing or esteem of an entity based on its past or present military performance, conduct, or capabilities.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6684a33688190b22cfc16907e76bc |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.