Triple
T486257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Bombers |
E9884
|
entity |
| Predicate | withdrewFromLeague |
P9372
|
FINISHED |
| Object | NBA in 1950 |
—
|
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: NBA in 1950 | Statement: [St. Louis Bombers, withdrewFromLeague, NBA in 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrewFromLeague Context triple: [St. Louis Bombers, withdrewFromLeague, NBA in 1950]
-
A.
withdrewFrom
chosen
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
-
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.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
-
D.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
E.
formerLeague
Indicates that an entity previously belonged to or participated in a particular league but is no longer a member.
- 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_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. |
Created at: Feb. 28, 2026, 1:12 p.m.