Triple
T22081784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian League |
E545666
|
entity |
| Predicate | formerPlayerType |
P146886
|
FINISHED |
| Object | professional minor league players |
—
|
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 minor league players | Statement: [Appalachian League, formerPlayerType, professional minor league players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPlayerType Context triple: [Appalachian League, formerPlayerType, professional minor league players]
-
A.
formerSport
Indicates that an entity previously played or participated in a particular sport but no longer does so.
-
B.
formerAthlete
Indicates that a person previously had the role or status of an athlete but no longer does.
-
C.
retiredAsPlayerFrom
Indicates that an individual ended their professional playing career while being associated with a specific team, organization, or context.
-
D.
teamTypePlayedFor
Indicates the type or category of team (e.g., national, club, youth) that an entity has played for.
-
E.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b706288190945c0c37e5ff2756 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:28 p.m.