Triple
T19854457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerie |
E477093
|
entity |
| Predicate | advertisingPractice |
P137581
|
FINISHED |
| Object | no airbrushing |
—
|
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: no airbrushing | Statement: [Aerie, advertisingPractice, no airbrushing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advertisingPractice Context triple: [Aerie, advertisingPractice, no airbrushing]
-
A.
advertises
Indicates that one entity promotes, publicizes, or markets another entity, typically to attract attention or customers.
-
B.
adType
Indicates the classification or category of an advertisement associated with an entity or event.
-
C.
marketingAs
Indicates that one entity is being presented, promoted, or branded to others as if it were another specified entity, role, or category.
-
D.
involvedCampaignAdvertising
Indicates that an entity participated in or contributed to the creation, distribution, or execution of campaign-related advertising activities.
-
E.
includesAdvertisingClause
Indicates that a contract or agreement contains a specific clause governing advertising-related rights, obligations, or restrictions.
- F. None of above. chosen
Provenance (4 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6586b5b088190948ef002c1e77176 |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.