Triple
T5093003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Jaguars football |
E114797
|
entity |
| Predicate | homeStateFanBase |
P60687
|
FINISHED |
| Object | Louisiana football fans |
—
|
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: Louisiana football fans | Statement: [Southern Jaguars football, homeStateFanBase, Louisiana football fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStateFanBase Context triple: [Southern Jaguars football, homeStateFanBase, Louisiana football fans]
-
A.
homeStateTeamOf
Indicates that one team is the designated home-state team associated with a particular person, organization, or region.
-
B.
homeState
Indicates that a person or organization has their primary residence, registration, or official base in a particular state.
-
C.
homeStateCompetition
Indicates a competitive event or rivalry that takes place within, or is specifically associated with, an entity’s home state.
-
D.
homeStateFlag
Indicates that a particular flag is officially recognized as the state flag of the referenced home state.
-
E.
homeNation
Indicates that one entity is the country or nation that serves as the primary home or origin for another entity.
- F. None of above. chosen
Provenance (4 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd754369708190bf4e171a904a19e1 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72b8d7a88190ad53fae64f17e22c |
completed | March 20, 2026, 4:15 p.m. |
Created at: March 20, 2026, 1:40 p.m.