Triple
T30340023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amen. (film) |
E771720
|
entity |
| Predicate | hasTitleCardDesign |
P185641
|
FINISHED |
| Object | minimalist cross and swastika logo |
—
|
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: minimalist cross and swastika logo | Statement: [Amen. (film), hasTitleCardDesign, minimalist cross and swastika logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCardDesign Context triple: [Amen. (film), hasTitleCardDesign, minimalist cross and swastika logo]
-
A.
hasTitleCard
Indicates that an entity is associated with a title card, such as an introductory or identifying screen or graphic.
-
B.
hasTitleCardFunction
Indicates that something serves the role or function of a title card, such as introducing or labeling content.
-
C.
hasOpeningTitleDesignBy
Indicates that an entity’s opening title sequence was designed or created by a specified designer or design entity.
-
D.
featuresTitleCards
Indicates that one entity includes or presents title cards as part of its content or structure.
-
E.
hasTitleOver
Indicates that one entity holds a formal title, rank, or designation in relation to another entity.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 29, 2026, 7:55 p.m.