Triple
T16512445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BankAtlantic |
E401091
|
entity |
| Predicate | brandUsedIn |
P42926
|
FINISHED |
| Object | BankAtlantic Center naming rights |
—
|
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: BankAtlantic Center naming rights | Statement: [BankAtlantic, brandUsedIn, BankAtlantic Center naming rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandUsedIn Context triple: [BankAtlantic, brandUsedIn, BankAtlantic Center naming rights]
-
A.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
-
B.
brandUsedInCountry
Indicates that a particular brand is used or present within a specified country.
-
C.
usedBrand
chosen
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
-
D.
usedInBrand
Indicates that something (such as a component, material, or element) is utilized as part of or within a particular brand.
-
E.
usedOnBrand
Indicates that something (such as a product, material, or element) is applied to, associated with, or utilized in connection with a particular brand.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e77d9b081909235cb5ba77d1e29 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.