Triple
T349721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gleiwitz incident |
E7414
|
entity |
| Predicate | mediaTypeInvolved |
P4793
|
FINISHED |
| Object | radio broadcast |
—
|
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: radio broadcast | Statement: [Gleiwitz incident, mediaTypeInvolved, radio broadcast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaTypeInvolved Context triple: [Gleiwitz incident, mediaTypeInvolved, radio broadcast]
-
A.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
B.
mediaOrigin
Indicates the original source or provenance from which a piece of media (such as an image, video, or audio) was derived or obtained.
-
C.
mediaAspect
Indicates the specific aspect ratio or dimensional proportion of a media item in relation to its width and height.
-
D.
usedByMedia
Indicates that something is employed or utilized by media organizations or media-related channels.
-
E.
usedMedium
chosen
Indicates that an action or communication was carried out through a particular medium or channel.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb1dc5f88190b54d084c6def7fc5 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.