Triple
T3060023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Bombers |
E60574
|
entity |
| Predicate | formerNBATeam |
P8967
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [St. Louis Bombers, formerNBATeam, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNBATeam Context triple: [St. Louis Bombers, formerNBATeam, true]
-
A.
NBAteam
Indicates that one entity is a professional basketball team that competes in the National Basketball Association (NBA) and the other entity is associated with it in that team role.
-
B.
formerSportsTeam
chosen
Indicates that an entity was once a member of or played for a particular sports team in the past but no longer does so.
-
C.
hasNBAFranchiseHistoryFrom
Indicates that an entity has a history of operating an NBA franchise originating from a specified location or organization.
-
D.
allNBATeam
Indicates that an entity (typically a player) has been selected to an All-NBA Team for a given season or time period.
-
E.
NBAChampionshipTeam
Indicates that a team has won the NBA championship title for a given season.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e9cf9188190b43f50edc009030d |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.