Triple
T6000650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Best a Man Can Get |
E133585
|
entity |
| Predicate | usedInCampaignType |
P672
|
FINISHED |
| Object | global advertising campaign |
—
|
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: global advertising campaign | Statement: [The Best a Man Can Get, usedInCampaignType, global advertising campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCampaignType Context triple: [The Best a Man Can Get, usedInCampaignType, global advertising campaign]
-
A.
campaignUse
Indicates that one entity employs or leverages another as part of a campaign or organized promotional effort.
-
B.
campaignType
chosen
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
C.
campaignUsage
Indicates how a campaign is utilized or applied within a particular context or system.
-
D.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
E.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee5e7bc8190aaa87605fa7b102e |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.