Triple
T2865680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsches Jungvolk |
E63431
|
entity |
| Predicate | roleInRegime |
P20515
|
FINISHED |
| Object | mass mobilization of youth |
—
|
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: mass mobilization of youth | Statement: [Deutsches Jungvolk, roleInRegime, mass mobilization of youth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRegime Context triple: [Deutsches Jungvolk, roleInRegime, mass mobilization of youth]
-
A.
roleInRepublic
Indicates that an entity holds or plays a specific role or function within a republic or republican system.
-
B.
associatedWithRegime
chosen
Indicates a relationship where an entity is linked or connected to a particular regime, such as a political, governmental, or ruling system.
-
C.
roleDuringColdWar
Indicates the specific position, function, or involvement an entity had in the context of the Cold War period.
-
D.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
E.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb9e64c819087b1a47caeb174d5 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.