Triple
T5251170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby City |
E118589
|
entity |
| Predicate | isPartOfBrandingFor |
P11989
|
FINISHED |
| Object | Louisville tourism marketing |
—
|
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: Louisville tourism marketing | Statement: [Derby City, isPartOfBrandingFor, Louisville tourism marketing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfBrandingFor Context triple: [Derby City, isPartOfBrandingFor, Louisville tourism marketing]
-
A.
isPartOfBrandStrategy
Indicates that an action, element, or decision is included within and contributes to the overall brand strategy.
-
B.
hasBranding
chosen
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
C.
hasBrandIdentityElement
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
D.
sponsorBrandType
Indicates the type or category of brand that is acting as a sponsor in the relationship.
-
E.
sharesBrandingWith
Indicates that two entities use the same or closely related branding elements, such as name, logo, or visual identity.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b7b840881908bb1ecb8a0047382 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.