Triple
T26387194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valdosta State Blazers football (offensive coordinator) |
E663312
|
entity |
| Predicate | sideCoached |
P24897
|
FINISHED |
| Object | offense |
—
|
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: offense | Statement: [Valdosta State Blazers football (offensive coordinator), sideCoached, offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideCoached Context triple: [Valdosta State Blazers football (offensive coordinator), sideCoached, offense]
-
A.
coachedAlongside
Indicates that two or more individuals served as coaches at the same time, typically for the same team, organization, or event.
-
B.
sideOfBallCoached
chosen
Indicates which side or unit of a ball (e.g., offense, defense, special teams) a coach is responsible for.
-
C.
secondaryCoach
Indicates that an entity serves as an assistant or secondary coach in relation to a primary coach or coaching role.
-
D.
coachedAgainst
Indicates that one person served as a coach of a team that competed in opposition to a team coached by another person.
-
E.
sideEngagementOf
Indicates a relationship where one entity is engaged with or attached to the side 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610bc2b288190ae10e6c27e5df786 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:23 p.m.