Triple
T30521522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldSSP |
E776703
|
entity |
| Predicate | audienceFormat |
P98534
|
FINISHED |
| Object | televised international series |
—
|
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: televised international series | Statement: [WorldSSP, audienceFormat, televised international series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceFormat Context triple: [WorldSSP, audienceFormat, televised international series]
-
A.
audienceSetting
Indicates the context or environment in which an audience is situated or addressed.
-
B.
hasAudienceFormat
chosen
Indicates that an entity is associated with a particular format or medium in which its audience receives or experiences it.
-
C.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
-
D.
audienceOrientation
Indicates how something is directed, tailored, or positioned with respect to a particular audience or group of recipients.
-
E.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6880b4a788190b7031f48ee4daf3a |
completed | May 2, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:17 p.m.