Triple
T486278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Bombers |
E9884
|
entity |
| Predicate | roleInLeagueHistory |
P14030
|
FINISHED |
| Object | charter-era BAA franchise |
—
|
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: charter-era BAA franchise | Statement: [St. Louis Bombers, roleInLeagueHistory, charter-era BAA franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLeagueHistory Context triple: [St. Louis Bombers, roleInLeagueHistory, charter-era BAA franchise]
-
A.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
B.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
-
C.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
D.
leaguePlayedIn
Indicates that a sports team or player has participated in competitions within a particular league.
-
E.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bc6f548190b13dee42cb100423 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.