Triple
T17077590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sra. Rushmore |
E414389
|
entity |
| Predicate | targetAudienceForClients |
P481
|
FINISHED |
| Object | mass consumer audiences |
—
|
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: mass consumer audiences | Statement: [Sra. Rushmore, targetAudienceForClients, mass consumer audiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAudienceForClients Context triple: [Sra. Rushmore, targetAudienceForClients, mass consumer audiences]
-
A.
targetOutcomeForClients
Indicates the specific result or benefit that an action, service, or process is intended to achieve for clients.
-
B.
intendedClients
Indicates the entities that a product, service, or action is specifically designed or targeted to serve as clients.
-
C.
targetMarket
chosen
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
D.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
E.
targetDevelopers
Indicates that something is specifically aimed at, intended for, or directed toward developers as its primary audience or users.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc625c48190b679a521180e10ad |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.