Triple
T28781133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Christians movement |
E726680
|
entity |
| Predicate | positionOnJesus |
P192912
|
FINISHED |
| Object | portrayed Jesus as an Aryan figure |
—
|
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: portrayed Jesus as an Aryan figure | Statement: [German Christians movement, positionOnJesus, portrayed Jesus as an Aryan figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnJesus Context triple: [German Christians movement, positionOnJesus, portrayed Jesus as an Aryan figure]
-
A.
placesJesusInLineOf
Indicates that one entity positions or situates Jesus within a particular lineage, sequence, or relational line connected to another entity.
-
B.
positionOnCreed
Indicates a person's stance, alignment, or viewpoint regarding a particular creed, doctrine, or set of beliefs.
-
C.
positionOnLiturgy
Indicates the stance or viewpoint an entity holds regarding liturgical practices, forms, or regulations.
-
D.
recognizesJesusWhen
Indicates that one entity identifies or acknowledges Jesus as such under certain conditions or at a particular time.
-
E.
positionOnSaints
Indicates a stance, view, or policy that an entity holds regarding saints or sainthood.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 28, 2026, 6:19 a.m.