Triple
T10785966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuppenheimer |
E254451
|
entity |
| Predicate | advertisingStyle |
P68438
|
FINISHED |
| Object | illustrated print ads |
—
|
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: illustrated print ads | Statement: [Kuppenheimer, advertisingStyle, illustrated print ads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advertisingStyle Context triple: [Kuppenheimer, advertisingStyle, illustrated print ads]
-
A.
brandingStyle
Indicates the specific visual and stylistic approach used to represent a brand’s identity.
-
B.
hasAdvertisingVisual
chosen
Indicates that an entity includes, is associated with, or uses a specific visual element or asset for advertising purposes.
-
C.
usesAdvertisingModel
Indicates that one entity employs or relies on another entity’s advertising-based business or revenue model.
-
D.
advertisingLocation
Indicates the place or medium where an advertisement is displayed or presented.
-
E.
hasAdvertisingSlogan
Indicates that an entity uses or is associated with a particular advertising slogan as part of its promotional or branding activities.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d44b488190a9f3ab9b177e737a |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.