Triple
T49202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball |
E967
|
entity |
| Predicate | isPremierLeagueFor |
P1767
|
FINISHED |
| Object | professional baseball in North America |
—
|
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: professional baseball in North America | Statement: [Major League Baseball, isPremierLeagueFor, professional baseball in North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPremierLeagueFor Context triple: [Major League Baseball, isPremierLeagueFor, professional baseball in North America]
-
A.
leaguePlayedIn
Indicates that a sports team or player has participated in competitions within a particular league.
-
B.
league
Indicates that an organization or team participates in, is a member of, or is associated with a particular sports or competitive league.
-
C.
hasProfessionalLeague
chosen
Indicates that an entity is associated with or participates in a recognized professional sports league.
-
D.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed 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.
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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.