Triple
T19592693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial to Homosexuals Persecuted under Nazism |
E470274
|
entity |
| Predicate | hasVideoContent |
P136383
|
FINISHED |
| Object | same-sex couples kissing |
—
|
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: same-sex couples kissing | Statement: [Memorial to Homosexuals Persecuted under Nazism, hasVideoContent, same-sex couples kissing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVideoContent Context triple: [Memorial to Homosexuals Persecuted under Nazism, hasVideoContent, same-sex couples kissing]
-
A.
hasMusicVideo
Indicates that a piece of media (typically a song) is associated with or accompanied by a music video.
-
B.
hasMusicVideoCharacteristic
Indicates that a music video possesses a specific attribute, feature, or quality.
-
C.
hasVideoRecording
Indicates that there exists an associated video recording capturing or documenting the referenced entity or event.
-
D.
hasOfficialVideo
Indicates that an entity is associated with an officially released video version or recording.
-
E.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
- F. None of above. chosen
Provenance (4 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64057460c8190962e2e58f06b3985 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.