Triple
T577433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DART for Advertisers |
E13785
|
entity |
| Predicate | providesFeature |
P203
|
FINISHED |
| Object | centralized ad trafficking interface |
—
|
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: centralized ad trafficking interface | Statement: [DART for Advertisers, providesFeature, centralized ad trafficking interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesFeature Context triple: [DART for Advertisers, providesFeature, centralized ad trafficking interface]
-
A.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
D.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
E.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
- 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.