Triple
T34098720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Agenda |
E874505
|
entity |
| Predicate | audienceTerm |
P72617
|
FINISHED |
| Object | producers |
—
|
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: producers | Statement: [No Agenda, audienceTerm, producers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceTerm Context triple: [No Agenda, audienceTerm, producers]
-
A.
audienceDescribedAs
Indicates that an audience is characterized or labeled using a particular description or set of attributes.
-
B.
audienceWith
Indicates that one entity formally meets or is granted an official interview or hearing with another, typically higher-status, entity.
-
C.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
D.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
-
E.
audienceRole
chosen
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.