Triple
T2409906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traverse City Pit Spitters |
E50362
|
entity |
| Predicate | usesPlayersFrom |
P13494
|
FINISHED |
| Object | college baseball programs |
—
|
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: college baseball programs | Statement: [Traverse City Pit Spitters, usesPlayersFrom, college baseball programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlayersFrom Context triple: [Traverse City Pit Spitters, usesPlayersFrom, college baseball programs]
-
A.
governsPlayersFrom
Indicates that an entity exercises authority or control over players originating from a specified source or group.
-
B.
featuresPlayersFrom
chosen
Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
-
C.
playsWith
Indicates that one entity engages in play or recreational activity together with another entity.
-
D.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
-
E.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:58 p.m.