Triple
T25042167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Explore Georgia |
E627140
|
entity |
| Predicate | typeOfMarketing |
P141955
|
FINISHED |
| Object | consumer 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: consumer marketing | Statement: [Explore Georgia, typeOfMarketing, consumer marketing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMarketing Context triple: [Explore Georgia, typeOfMarketing, consumer marketing]
-
A.
marketingAs
Indicates that one entity is being presented, promoted, or branded to others as if it were another specified entity, role, or category.
-
B.
marketingMessageType
chosen
Indicates the specific category or kind of marketing message being used or communicated in the relationship.
-
C.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
D.
isMarketingRelated
Indicates that something is associated with, pertains to, or is relevant to marketing activities, strategies, or objectives.
-
E.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 18, 2026, 6:08 a.m.