Triple
T3473252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Ads |
E73311
|
entity |
| Predicate | supportsCampaignGoal |
P39536
|
FINISHED |
| Object | sales |
—
|
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: sales | Statement: [Google Ads, supportsCampaignGoal, sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCampaignGoal Context triple: [Google Ads, supportsCampaignGoal, sales]
-
A.
supportGoal
Indicates that one entity actively helps, promotes, or contributes to the achievement of another entity’s goal.
-
B.
supportsPolicyGoal
chosen
Indicates that one entity’s actions, positions, or characteristics help advance, uphold, or contribute to achieving a specified policy goal.
-
C.
statedAsGoalFor
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
D.
supportPercentage
Indicates the proportion or share of total backing, approval, or assistance that one entity provides to or receives from another, typically expressed as a percentage.
-
E.
campaignPromise
Indicates that an individual or organization has made a public commitment to take a specific action or pursue a particular policy as part of a campaign.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3e03e081908aa09291bbf351bd |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.