Triple
T4908567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlington Bees |
E109972
|
entity |
| Predicate | formerlyMiLB |
P40951
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Burlington Bees, formerlyMiLB, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyMiLB Context triple: [Burlington Bees, formerlyMiLB, Yes]
-
A.
minorLeagueSystem
Indicates that one sports organization serves as the developmental or affiliated minor-league system for another, typically higher-level, organization.
-
B.
playedInMinorLeagues
Indicates that an individual participated as a player in one or more minor league sports teams or competitions.
-
C.
minorLeagueOrganization
Indicates that one organization functions as a minor league affiliate or developmental partner of another, typically higher-level, sports organization.
-
D.
hasMinorLeagueStatus
chosen
Indicates that an entity holds a classification or designation as belonging to a minor league level within a hierarchical league system.
-
E.
minorLeagueManagerFor
Indicates that one entity serves as the manager of a minor league team associated with another entity (typically a professional sports organization).
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e765094819099481f4f2dd7c47d |
completed | March 20, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.