Triple
T35288435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixar Pals |
E1019154
|
entity |
| Predicate | brandingUsedAt |
P23474
|
FINISHED |
| Object | Disneyland Resort |
—
|
NE NERFINISHED |
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: Disneyland Resort | Statement: [Pixar Pals, brandingUsedAt, Disneyland Resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandingUsedAt Context triple: [Pixar Pals, brandingUsedAt, Disneyland Resort]
-
A.
brandingVisibleOn
Indicates that the branding or logo of one entity is visibly displayed on another entity.
-
B.
brandNameUsedIn
Indicates that a particular brand name is used or appears within a specified context, such as a product, document, or communication.
-
C.
brandingThrough
Indicates that one entity promotes, communicates, or shapes the identity of another entity by means of a specific brand or branding activity.
-
D.
brandUsage
chosen
Indicates that one entity uses, features, or is associated with another entity’s brand in its products, services, or communications.
-
E.
brandingAuthority
Indicates that one entity has the recognized power or right to define, control, or approve the branding (name, logo, identity, or brand usage) of another entity or product.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:03 p.m.