Triple
T13518154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudy Steiner |
E322820
|
entity |
| Predicate | isForcedInto |
P4672
|
FINISHED |
| Object | Nazi youth training |
—
|
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: Nazi youth training | Statement: [Rudy Steiner, isForcedInto, Nazi youth training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isForcedInto Context triple: [Rudy Steiner, isForcedInto, Nazi youth training]
-
A.
forcedBy
chosen
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
B.
enteredIntoForce
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
-
C.
enteredIntoForceIn
Indicates that an agreement, law, or treaty became legally effective or operative in a specified place or jurisdiction.
-
D.
isForcedToConvertTo
Indicates that one entity is compelled, against its will, to change its beliefs, affiliation, or status to match that of another entity.
-
E.
enteredIntoForceBy
Indicates that a legal instrument, agreement, or provision became legally effective as a result of an action taken by a specified authority, event, or instrument.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa27f048190bed33a98e28c8d09 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:44 p.m.