Triple
T28218023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Battlehawks |
E711370
|
entity |
| Predicate | conferenceOrDivisionRival |
P52336
|
FINISHED |
| Object | DC Defenders |
—
|
NE NERFINISHED |
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: DC Defenders | Statement: [St. Louis Battlehawks, conferenceOrDivisionRival, DC Defenders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceOrDivisionRival Context triple: [St. Louis Battlehawks, conferenceOrDivisionRival, DC Defenders]
-
A.
conferenceRivalry
chosen
Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
-
B.
competitionConference
Indicates that a competition is associated with, held at, or organized as part of a particular conference.
-
C.
conferenceOrLeagueChampionship
Indicates that an entity has won or holds a championship title in its conference or league.
-
D.
hasConferenceOrDivision
Indicates that an entity is associated with a specific conference or division within a larger organizational or competitive structure.
-
E.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 10:44 p.m.