Triple
T22151696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International League (original) |
E547428
|
entity |
| Predicate | playerPipelineRole |
P106653
|
FINISHED |
| Object | stepping stone to 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: stepping stone to Major League Baseball | Statement: [International League (original), playerPipelineRole, stepping stone to Major League Baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerPipelineRole Context triple: [International League (original), playerPipelineRole, stepping stone to Major League Baseball]
-
A.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
B.
talentPipelineRole
chosen
Indicates a role that an entity holds or plays within a talent acquisition or development pipeline.
-
C.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
-
D.
gameRoleForPlayers
Indicates the specific role or function that players have within a particular game or gameplay context.
-
E.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f4b05c8190a824f55804f6d4d5 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.