Triple
T32035692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polizeiruf 110 |
E818087
|
entity |
| Predicate | hasAudienceIn |
P793
|
FINISHED |
| Object | Germany |
—
|
NE NERFINISHED |
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: Germany | Statement: [Polizeiruf 110, hasAudienceIn, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceIn Context triple: [Polizeiruf 110, hasAudienceIn, Germany]
-
A.
hasAudience
chosen
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
hasAudienceAddress
Indicates that an entity delivers or directs a message, speech, or communication specifically toward a particular audience.
-
C.
hasAudienceAssociation
Indicates that there is a defined relationship between an entity and a specific audience or audience group with which it is associated.
-
D.
hasAudiencePolicy
Indicates that there is a specified rule or policy governing which audience or group is allowed to access, view, or receive something.
-
E.
hasAudienceLevel
Indicates that something is intended for, suitable for, or targeted at an audience with a specific level of knowledge, experience, or proficiency.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:18 a.m.