Triple
T24762736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toledo Blue Stockings |
E619492
|
entity |
| Predicate | leagueMembershipChange |
P157103
|
FINISHED |
| Object | joined American Association in 1884 |
—
|
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: joined American Association in 1884 | Statement: [Toledo Blue Stockings, leagueMembershipChange, joined American Association in 1884]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueMembershipChange Context triple: [Toledo Blue Stockings, leagueMembershipChange, joined American Association in 1884]
-
A.
clubMembership
Indicates that an entity belongs to, is enrolled in, or holds membership status within a particular club.
-
B.
leagueAffected
Indicates that a particular league is impacted or influenced by a specified event, action, or condition.
-
C.
leagueRenamedAs
Indicates that a sports league has changed its official name to a new one.
-
D.
membershipTransfer
Indicates the transfer of membership status, rights, or affiliation from one entity to another.
-
E.
footballMembership
Indicates that an entity belongs to, is part of, or holds membership in a football-related organization, team, 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a330f0819081bc60b9275d883d |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:27 a.m.