Triple
T37607817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwinnett Braves |
E935702
|
entity |
| Predicate | rebrandEffectiveSeason |
P111911
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Gwinnett Braves, rebrandEffectiveSeason, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebrandEffectiveSeason Context triple: [Gwinnett Braves, rebrandEffectiveSeason, 2018]
-
A.
rebrandPeriod
Indicates the time span during which an entity undergoes or is designated for a rebranding.
-
B.
rebrandedWithNetwork
Indicates that an entity has undergone a rebranding that includes or is associated with a specific network or network-related identity.
-
C.
clubRenameEffectiveSeason
chosen
Indicates the season from which a club’s new name officially takes effect.
-
D.
acquisitionEffectiveSeason
Indicates the season during which an acquisition becomes officially effective or takes effect.
-
E.
rebrandingProgram
Indicates a program or initiative through which an entity changes or updates its brand identity, such as its name, logo, or overall image.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.