Triple
T1477679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Providence Steamrollers |
E30879
|
entity |
| Predicate | historicalLeagueStatus |
P14030
|
FINISHED |
| Object | precursor to the modern NBA |
—
|
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: precursor to the modern NBA | Statement: [Providence Steamrollers, historicalLeagueStatus, precursor to the modern NBA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLeagueStatus Context triple: [Providence Steamrollers, historicalLeagueStatus, precursor to the modern NBA]
-
A.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
B.
footballStatusHistory
Indicates the recorded progression of statuses or conditions related to a football entity over time.
-
C.
leagueContext
Indicates the broader league or competition setting within which the relationship or action takes place.
-
D.
stateLeague
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
-
E.
roleInLeagueHistory
chosen
Indicates the specific function, contribution, or significance an entity has had within the historical development or narrative of a league.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c605d4c0819088ab06678b2ba6f3 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.