Triple
T5866645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amateur Basketball Association of the United States of America |
E130410
|
entity |
| Predicate | rebrandedInYear |
P48649
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Amateur Basketball Association of the United States of America, rebrandedInYear, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebrandedInYear Context triple: [Amateur Basketball Association of the United States of America, rebrandedInYear, 1989]
-
A.
announcedRebrandingAs
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
-
B.
introducedAsBrandBy
Indicates that one entity was presented or launched to the public or a market as a brand by another entity.
-
C.
brandLaunchYear
Indicates the calendar year in which a brand was first introduced or launched to the market.
-
D.
brandingChangeDate
chosen
Indicates the date on which a change in branding (such as name, logo, or visual identity) took effect.
-
E.
reintroducedInYear
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.