Triple
T1521592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily Mirror |
E32240
|
entity |
| Predicate | originalTargetAudience |
P10804
|
FINISHED |
| Object | women |
—
|
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: women | Statement: [Daily Mirror, originalTargetAudience, women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTargetAudience Context triple: [Daily Mirror, originalTargetAudience, women]
-
A.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
secondaryAudience
Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
-
C.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
D.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
E.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.