Triple
T22727013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL Strikeout Leader |
E562022
|
entity |
| Predicate | leagueRestriction |
P149473
|
FINISHED |
| Object | National League teams |
—
|
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: National League teams | Statement: [NL Strikeout Leader, leagueRestriction, National League teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueRestriction Context triple: [NL Strikeout Leader, leagueRestriction, National League teams]
-
A.
sportRestriction
Indicates a limitation, prohibition, or specific condition placed on participating in a sport or sports-related activity.
-
B.
teamEligibility
Indicates whether an entity meets the required conditions to participate as a member of a particular team.
-
C.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
D.
professionalPlayersAllowedFrom
Indicates that professional players are permitted to participate starting from a specified point, such as a date, level, or stage.
-
E.
associatedLeagueRuleAdoption
Indicates that there is a connection between an entity and the specific league rule adoption that governs or influences it.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792a2ee48190bfbdde1a72adfd25 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:20 p.m.