Triple
T577419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DART for Advertisers |
E13785
|
entity |
| Predicate | targetingCapability |
P860
|
FINISHED |
| Object | site targeting |
—
|
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: site targeting | Statement: [DART for Advertisers, targetingCapability, site targeting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetingCapability Context triple: [DART for Advertisers, targetingCapability, site targeting]
-
A.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
D.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
E.
primaryCapability
Indicates that one entity serves as the main or most important functional ability, role, or competence of another entity.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b68cc808190b1ba45bdad78443d |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.