Triple
T4765906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Blues |
E105808
|
entity |
| Predicate | historicalLeagueClassification |
P10472
|
FINISHED |
| Object | pre-modern Major League Baseball |
—
|
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: pre-modern Major League Baseball | Statement: [Cleveland Blues, historicalLeagueClassification, pre-modern Major League Baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLeagueClassification Context triple: [Cleveland Blues, historicalLeagueClassification, pre-modern Major League Baseball]
-
A.
divisionOrConferenceHistory
Indicates the historical record of which divisions or conferences an entity has belonged to over time.
-
B.
leagueType
chosen
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
C.
leagueContext
Indicates the broader league or competition setting within which the relationship or action takes place.
-
D.
formerLeague
Indicates that an entity previously belonged to or participated in a particular league but is no longer a member.
-
E.
winnerLeagueDivision
Indicates that an entity has won a specific league division in a competitive context.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.