Triple
T30613680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Ernst John von Freyend (Valkyrie) |
E779255
|
entity |
| Predicate | loyaltyInStory |
P94124
|
FINISHED |
| Object | Adolf Hitler |
—
|
NE NERFINISHED |
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: Adolf Hitler | Statement: [Major Ernst John von Freyend (Valkyrie), loyaltyInStory, Adolf Hitler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyInStory Context triple: [Major Ernst John von Freyend (Valkyrie), loyaltyInStory, Adolf Hitler]
-
A.
loyaltyRevealedIn
Indicates that an entity’s loyalty becomes evident or is demonstrated through a particular situation, action, or context.
-
B.
loyaltyDimension
Indicates the degree or aspect of loyalty characterizing the relationship between entities.
-
C.
isLoyalTo
chosen
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
D.
loyaltyReason
Indicates the reason or motivation behind one entity’s loyalty or allegiance to another.
-
E.
loyaltyTheme
Indicates a thematic relationship where one entity is centrally concerned with, expresses, or explores the concept of loyalty in relation to another entity.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689e8dfe4819087b2c5f7ee54151e |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.