Triple
T28781134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Christians movement |
E726680
|
entity |
| Predicate | positionOnJews |
P128804
|
FINISHED |
| Object | hostile |
—
|
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: hostile | Statement: [German Christians movement, positionOnJews, hostile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnJews Context triple: [German Christians movement, positionOnJews, hostile]
-
A.
positionOnJerusalem
Indicates that one entity occupies or is located at a specific position within the area of Jerusalem.
-
B.
policyTowardJews
chosen
Indicates a stance, approach, or set of actions that an entity adopts specifically in relation to Jewish people.
-
C.
positionOnJewishLaw
Indicates a relationship where one entity expresses or holds a particular stance, view, or interpretation regarding matters of Jewish law.
-
D.
relationshipToJews
Indicates how an entity is related or connected to Jewish people, communities, or Judaism.
-
E.
hasSignificantJewishCommunity
Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 28, 2026, 6:19 a.m.