Triple
T22081838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlington Royals |
E545667
|
entity |
| Predicate | operatedAsProfessionalTeamUntil |
P146891
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Burlington Royals, operatedAsProfessionalTeamUntil, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsProfessionalTeamUntil Context triple: [Burlington Royals, operatedAsProfessionalTeamUntil, 2020]
-
A.
operatedAsProfessionalTeam
Indicates that the entities functioned or were recognized as a professional sports team, rather than an amateur or informal organization.
-
B.
ownedProfessionalBaseballTeamUntil
Indicates that one entity owned a professional baseball team up to a specified end time or until a particular condition was met.
-
C.
playedForTeamEnd
Indicates that an entity’s period of playing for a particular team ended at a specified time or event.
-
D.
teamEndYear
Indicates the year in which an entity’s association with a particular team ended.
-
E.
laterPlayedFor
Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
- 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.