Triple
T33287546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voices of the left |
E852219
|
entity |
| Predicate | describesAudience |
P157946
|
FINISHED |
| Object | left-wing readers |
—
|
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: left-wing readers | Statement: [Voices of the left, describesAudience, left-wing readers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesAudience Context triple: [Voices of the left, describesAudience, left-wing readers]
-
A.
audienceDescribedAs
chosen
Indicates that an audience is characterized or labeled using a particular description or set of attributes.
-
B.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
C.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
D.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
-
E.
audienceRequirement
Indicates that a certain type or level of audience is required or expected for something (e.g., an event, work, or activity).
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:32 a.m.