Triple
T31877695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasty Boys |
E813786
|
entity |
| Predicate | leagueAffiliationDuringPeak |
P125837
|
FINISHED |
| Object | National League |
—
|
NE NERFINISHED |
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: National League | Statement: [Nasty Boys, leagueAffiliationDuringPeak, National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueAffiliationDuringPeak Context triple: [Nasty Boys, leagueAffiliationDuringPeak, National League]
-
A.
winnerLeagueAffiliationAtTime
Indicates that an entity is affiliated with a particular league at the time when it is the winner of a specified competition or event.
-
B.
leagueAffiliationHistory
chosen
Indicates the historical sequence of leagues or organizations with which an entity has been affiliated over time.
-
C.
playerAffiliation
Indicates the organization, team, or group with which a player is formally associated or aligned.
-
D.
seasonMostAssociatedWith
Indicates the season with which something is most strongly or typically associated compared to other seasons.
-
E.
leagueAffiliationThroughRole
Indicates that an entity is affiliated with a league specifically by virtue of a particular role or position it holds.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 30, 2026, 11:55 p.m.